<html> <head> <base href="https://bugs.documentfoundation.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_UNCONFIRMED " title="UNCONFIRMED - MACOS: Small memory leaks when discarding document recovery" href="https://bugs.documentfoundation.org/show_bug.cgi?id=114456#c3">Comment # 3</a> on <a class="bz_bug_link bz_status_UNCONFIRMED " title="UNCONFIRMED - MACOS: Small memory leaks when discarding document recovery" href="https://bugs.documentfoundation.org/show_bug.cgi?id=114456">bug 114456</a> from <a class="email" href="mailto:iplaw67@tuta.io" title="Alex Thurgood <iplaw67@tuta.io>"> Alex Thurgood</a> <pre>(In reply to Telesto from <a href="show_bug.cgi?id=114456#c2">comment #2</a>) > Small addition. I'm rather often noticing small leaks (as in this case) when > interacting with the GUI: > _DPSNextEvent > NSEventAuxiliary > NSCopyObject > CGEvent SkyLight SLTypeCreateInstance > _NSLocalEventObserver NSEvent > ddLocalMonitorForEventsMatchingMask:placement:handler:] > > I haven't reported them separately, because the responsible library comes > from Apple... Or can this be fixed in the LibreOffice code? Yes, I have noticed this too. If it is Apple's code, there probably isn't much we can do. When I tried hunting down some of these via Instruments to the source code, I just ended up in the assembler instructions, so there probably isn't anything we can do. If there is Apple code that we include for which the source is available (e.g. because we have included it in our git repo) then at least we could point out to Apple where the problem might lie, but if it just points to some assembler, I'm assuming we're not going to have access to any sort of other source code. Of course, someone competent enough in disassembly might be able to do something with it, but would that go against Apple's Developer T&Cs ?</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>