<html>
<head>
<base href="https://bugs.documentfoundation.org/">
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW - CRASH when resize/shrink image in CALC"
href="https://bugs.documentfoundation.org/show_bug.cgi?id=132694#c9">Comment # 9</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW - CRASH when resize/shrink image in CALC"
href="https://bugs.documentfoundation.org/show_bug.cgi?id=132694">bug 132694</a>
from <span class="vcard"><a class="email" href="mailto:ilmari.lauhakangas@libreoffice.org" title="Buovjaga <ilmari.lauhakangas@libreoffice.org>"> <span class="fn">Buovjaga</span></a>
</span></b>
<pre>(In reply to Telesto from <a href="show_bug.cgi?id=132694#c8">comment #8</a>)
<span class="quote">> Same mem usage on 6.4.3?</span >
Good point: it is catastrophic with 6.4.3 and sadly with 6.4.4 as well. Only
way out is Ctrl-Alt-backspace.
The good news is that when I tried with bibisect repo 6.5, I can repo the
catastrophe in the oldest and then 1000 commits before master, I see a state
where there is NO memory hogging. So I should be able to both reverse-bisect
the fix to the catastrophy AND bisect the cause of the more minor memory
hogging seen in current master.
I don't have time to do this immediately, though. Maybe in a couple of hours or
more.</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>