https://bugs.freedesktop.org/show_bug.cgi?id=46805
--- Comment #9 from tommy27 <[email protected]> 2012-04-13 12:09:14 PDT --- I report here a private mail from Michael Meeks about this bug, giving instructions to debug: So - then we need a profile of the piece that is slow; do you have a Linux machine you can repeat this on ? If so, can you run libreoffice under callgrind like this: export OOO_DISABLE_RECOVERY=1 valgrind --tool=callgrind --simulate-cache=yes --dump-instr=yes ./soffice.bin -writer --splash-pipe=0 Select your dictionary (beware it runs 80x slower than normal or so ;-). Then you'd want to gzip up the callgrind.out.... and attach it to the bug - that'll help the developers ~immediately fix the problem, and save them lots of time. The fix is prolly only a few minutes if we have that data, and it's more likely to get done. A linux VM would be fine to do the profiling. .......... unfortunately I have no experience with Linux so I can not run this text. is there any "penguin" right here that may help? -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug. _______________________________________________ Libreoffice-bugs mailing list [email protected] http://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
