https://bugs.documentfoundation.org/show_bug.cgi?id=108246

Buovjaga <[email protected]> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
           Keywords|                            |perf
           Priority|medium                      |high
             Status|UNCONFIRMED                 |NEW
                 CC|                            |[email protected]
            Version|5.3.3.2 release             |5.2.0.4 release
     Ever confirmed|0                           |1
           Severity|normal                      |major

--- Comment #8 from Buovjaga <[email protected]> ---
I think this might give more insight to developers:
https://wiki.documentfoundation.org/QA/BugReport/Debug_Information#GNU.2FLinux:_How_to_get_a_callgrind_trace

The way I do it is I have this stored in a text file and then I just paste the
whole thing into a terminal:

unset MALLOC_CHECK_
unset MALLOC_PERTURB_
unset G_SLICE
export SAL_DISABLE_FLOATGRAB=1
export OOO_DISABLE_RECOVERY=1
export SAL_DISABLE_GL_WATCHDOG=1
valgrind --tool=callgrind --simulate-cache=yes --dump-instr=yes
/path/to/program/soffice.bin --splash-pipe=0 

I guess let it chug there for a while and then close. The large callgrind file
compresses quite well with tar.xz and should fit inside our 10MB attachment
limit.

If you want to test older versions than 5.2:
https://wiki.documentfoundation.org/Installing_in_parallel/Linux

-- 
You are receiving this mail because:
You are the assignee for the bug.
_______________________________________________
Libreoffice-bugs mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs

Reply via email to