https://bugs.documentfoundation.org/show_bug.cgi?id=159529
--- Comment #6 from Patrick Luby <guibomac...@gmail.com> --- (In reply to Telesto from comment #5) > @Patrick > (In reply to Caolán McNamara from comment #4) > > Ideally we could get a massif profile to get a better view of what is eating > > the memory there, but I guess that's challenging on macOS. > > Any advice here? Valgrind and macOS is not easy to setup (if it currently > works at all). The Apple Instruments tools surely has heap/leak detection, > but unsure if it matches Valgrind kind of profiling The nightly master Mac Silicon builds have the necessary settings for Xcode's Instruments appplication to perform leak analysis and other performance analysis. My shortcut to open Instruments from the Terminal since it is hidden in Xcode's application bundle: open /Applications/Xcode.app/Contents/Applications/Instruments.app IIRC, the Mac Intel nightly builds don't have the necessary settings due to cross-compiling. But, if you do a local Mac Intel build, Instruements should be able to attach to it. Unfortunately, I am unable to look at this bug this week as I am buried in non-coding work this month. But when I get time, I see if Instruments shows anything. I did run Intruments when I first saw this bug and when I started leak detection before opening a Calc document and then stopping before closing Calc, IIRC the "heaviest stack" was in Skia retaining CGFont instances. Interestingly, if I didn't stop the leak detection until after I closed the Calc document, potential leaks dropped to only a few K of memory (likely global variables). I am writing from memory so all this may not be accurate, but maybe one area to look at is if Skia is holding onto CGFonts longer than necessary after drawing text. -- You are receiving this mail because: You are the assignee for the bug.
