<html>
<head>
<base href="https://bugs.documentfoundation.org/">
</head>
<body><span class="vcard"><a class="email" href="mailto:glogow@fbihome.de" title="Jan-Marek Glogowski <glogow@fbihome.de>"> <span class="fn">Jan-Marek Glogowski</span></a>
</span> changed
<a class="bz_bug_link
bz_status_NEEDINFO "
title="NEEDINFO - FILEOPEN DOCX: LO steadily increases memory usage until system freezes"
href="https://bugs.documentfoundation.org/show_bug.cgi?id=131651">bug 131651</a>
<br>
<table border="1" cellspacing="0" cellpadding="8">
<tr>
<th>What</th>
<th>Removed</th>
<th>Added</th>
</tr>
<tr>
<td style="text-align:right;">CC</td>
<td>
</td>
<td>thb@libreoffice.org
</td>
</tr>
<tr>
<td style="text-align:right;">Status</td>
<td>NEW
</td>
<td>NEEDINFO
</td>
</tr></table>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEEDINFO "
title="NEEDINFO - FILEOPEN DOCX: LO steadily increases memory usage until system freezes"
href="https://bugs.documentfoundation.org/show_bug.cgi?id=131651#c19">Comment # 19</a>
on <a class="bz_bug_link
bz_status_NEEDINFO "
title="NEEDINFO - FILEOPEN DOCX: LO steadily increases memory usage until system freezes"
href="https://bugs.documentfoundation.org/show_bug.cgi?id=131651">bug 131651</a>
from <span class="vcard"><a class="email" href="mailto:glogow@fbihome.de" title="Jan-Marek Glogowski <glogow@fbihome.de>"> <span class="fn">Jan-Marek Glogowski</span></a>
</span></b>
<pre>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 <a href="https://wiki.documentfoundation.org/Development/How_to_debug">https://wiki.documentfoundation.org/Development/How_to_debug</a>
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.</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the assignee for the bug.</li>
</ul>
</body>
</html>