<html> <head> <base href="https://bugs.documentfoundation.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_UNCONFIRMED " title="UNCONFIRMED - FreetypeFontInstance use-after-free during CppunitTest_sw_dialogs_test" href="https://bugs.documentfoundation.org/show_bug.cgi?id=121030#c3">Comment # 3</a> on <a class="bz_bug_link bz_status_UNCONFIRMED " title="UNCONFIRMED - FreetypeFontInstance use-after-free during CppunitTest_sw_dialogs_test" href="https://bugs.documentfoundation.org/show_bug.cgi?id=121030">bug 121030</a> from <a class="email" href="mailto:glogow@fbihome.de" title="Jan-Marek Glogowski <glogow@fbihome.de>"> Jan-Marek Glogowski</a> <pre>Nice backtraces. With this additional info it is clear what is happening here. The Freetype font cache is separate layer, below LO's general font cache, but it is not refcount handled, so this clear renders all cached font instances in the SalLayoutGlyphs invalid on UNIX. What is missing now is the invalidation of the FreetypeFont pointer when cleaning that font cache, as it has a map of all logical font instances. This can be detected by the cached SalLayoutGlyphsInpl, so it can invalidate itself, by returning empty(), which will result in a new valid cache. I'll do a fix tomorrow, unless you or someone else beats me to it. And probably getting rid of the GlyphCache and FreetypeFont, merging the functionality into the general FontCache.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>