<html>
<head>
<base href="https://bugs.documentfoundation.org/">
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_UNCONFIRMED "
title="UNCONFIRMED - Memory after third opening 280 MB expected 130 MB"
href="https://bugs.documentfoundation.org/show_bug.cgi?id=134026#c3">Comment # 3</a>
on <a class="bz_bug_link
bz_status_UNCONFIRMED "
title="UNCONFIRMED - Memory after third opening 280 MB expected 130 MB"
href="https://bugs.documentfoundation.org/show_bug.cgi?id=134026">bug 134026</a>
from <span class="vcard"><a class="email" href="mailto:telesto@surfxs.nl" title="Telesto <telesto@surfxs.nl>"> <span class="fn">Telesto</span></a>
</span></b>
<pre>(In reply to Buovjaga from <a href="show_bug.cgi?id=134026#c2">comment #2</a>)
<span class="quote">> I repro, but why open this when <a class="bz_bug_link
bz_status_ASSIGNED "
title="ASSIGNED - Memory usage increases after every file-reload"
href="show_bug.cgi?id=132536">bug 132536</a> still does not have a solution?</span >
Because I'm using the bugtracker as reminder to look at it some time; I
probably forget it.. at some point. And because I'm getting slightly
impatient..
* While testing bug I end up with 1/2 GB ram used.. with documents of 15 pages
in around 15 minutes.. I can only assume.. its the font cache, it's font
cache.. but never knowing for sure.. maybe another change..
* Font cache is tricky area.. Developers tend to walk around it for years. And
Khaled wasn't to happy with it either (and struggled to understand how it
worked).. So I assume the font cache to be a quite a thing; even for
experienced developers. Which makes me even more worrisome. And I connecting
this with the work of M. Stahl on tables, solve 1 problem, get 2 back. Solve
two problems get 4 back..
Or Jmux starting to fiddle with timers, madness appears everywhere
(re-resurrecting old hideous bugs etc). So I'm assuming the worst case.. until
I'm proven wrong... Especially with fonts/ font measurements being cached/used
on different levels. Harfbuzz Internal/ LibreOffice itself?/ the layout cache
of Miklos.. all relaying on font lifetime cycles etc. Different font handling
between OSes.. So enough potential to go wrong. It started already with welding
the Fontbox; adding of a new special rendering; removing a few font caches..
This type of rework you ideally plan in advance to do, not something you want
to resolve as side effect of welding; Ideally at the beginning of a new
release, not at the point of beta2 or RC1...
And a developer delaying to look at - I assume so; can't proof, maybe looking
at it in silence - it doesn't give me much confidence. I don't associate Caolan
in addition with font handling in general (more the expertise of Jmux/Khaled)
and/or
developing on Windows. Caolan has tons of experience... so maybe
underestimating (hope so) but I don't see it as his area of expertise (or
interest?). Especially if the font cache code being broken all over the place..
So fiddle with A and B does something unexpected. Fiddle with C and D does
something it shouldn't do. Fiddle with E, expect G and get Z.
I'm too pessimistic, I hope..</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>