https://bugs.documentfoundation.org/show_bug.cgi?id=131651
Jan-Marek Glogowski <[email protected]> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |[email protected]
Status|NEW |NEEDINFO
--- Comment #19 from Jan-Marek Glogowski <[email protected]> ---
Just gave it a quick test, with my master, bibisect-6-4 and bibisect-6-5 master
checkouts and I can't reproduce. I used a fresh profile and both documents
using kf5.
so -env:UserInstallation=file:///tmp/mem /tmp/doc*.docx
LO starts with 100% CPU but completely settles after a few seconds with
constant memory and no CPU load. I'm also on Debian Buster, FWIW.
Best bet would be to get some callgrind / perf log. See performance debugging
in https://wiki.documentfoundation.org/Development/How_to_debug
While callgrind is much slower, its logs are also much smaller. So if you can't
or don't want to debug this yourself, you probably want to run callgrind -
instead of perf - for a while (on that HW probably 30m+).
My first guess was "just" an other Writer idle layout problem, but that should
normally utilize a full core, which doesn't seem to happen for you, and the
memory gets leaked very slow (3% in 15m of 7.5GB), so I'm quite probably wrong.
If there was a parsing problem with the new footnote code, it would probably
exhaust the memory really fast.
Still in the end this would mean blind fixing for me without a reproducer, so I
doubt I can help.
--
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
