https://bugs.documentfoundation.org/show_bug.cgi?id=167455
--- Comment #13 from Patrick (volunteer) <[email protected]> --- (In reply to Patrick (volunteer) from comment #12) > Anyway, I think we have 2 choices here: > 1. Revert my patch and watch memory usage explode for *all* macOS users > (like an extra GB or two) > 2. I must write another "dangerous" modification to HarfBuzz to force a font > to repopulate its glyph cache after it has been flushed. It is kind of ironic that the developer who caused the HarfBuzz memory problems on macOS (and which I have been trying to clean up) thinks my patch is dangerous. Yet, HarfBuzz has no public API for flushing a font's glyph cache and since @Khaled's code holds onto a HarfBuzz font instance of every system font until LibreOffice is quit, holding all those font instances without flushing their glyph caches is not a reasonable approach on macOS. Sure, I could rewrite @Khaled's vcl implementation and continually delete a HarfBuzz font immediately after accessing its glyphs but I really don't have any spare time to implement font swapping in vcl. So it looks like another "dangerous" patch is our only option. -- You are receiving this mail because: You are the assignee for the bug.
