Description: MACOS: Small memory leaks when discarding document recovery Steps to Reproduce: 1. Open Writer with multiple (empty) documents 2. Force quite 3. Start the Instruments 4. Choose Memory Leak profile tool 5. Select LibreOffice.app in instdir as target process 6. Click on the record button, LODev is started by the profiling tool 7. Discard the document recovery (and don't save any recovery file) Actual Results: Multiple leaks Expected Results: No leaks Reproducible: Always User Profile Reset: No Additional Info: Version: 6.1.0.0.alpha0+ Build ID: d46dc8e547810208287aab77f0313f1971901464 CPU threads: 4; OS: Mac OS X 10.12.6; UI render: default; TinderBox: MacOSX-x86_64@49-TDF, Branch:master, Time: 2017-12-08_10:35:46 Locale: nl-NL (nl_NL.UTF-8); Calc: group threaded User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_12_6) AppleWebKit/603.3.8 (KHTML, like Gecko) Version/10.1.2 Safari/603.3.8
Created attachment 138437 [details] Screenshot
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?
(In reply to Telesto from comment #2) > 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 ?
Hi Telesto, Are the leaks originally reported still present in master? Regarding the ones in comment 2, as Alex mentioned, probably there isn't much we can do... I have set the bug's status to 'NEEDINFO'. Please change it back to 'UNCONFIRMED' if the bug is still present in the master build
Created attachment 139332 [details] A leaking backtrace with symbols Repro with Version: 6.1.0.0.alpha0+ Build ID: d1bc14b318c9a412a761d243085da0895a1aed4a CPU threads: 4; OS: Mac OS X 10.13.1; UI render: default; Locale: nl-NL (nl_US.UTF-8); Calc: group threaded
Hi Telesto, I guess the leaks are still happening on master ?
(In reply to Xisco Faulí from comment #6) > Hi Telesto, > I guess the leaks are still happening on master ? Setting to NEEDINFO...
Dear Telesto, This bug has been in NEEDINFO status with no change for at least 6 months. Please provide the requested information as soon as possible and mark the bug as UNCONFIRMED. Due to regular bug tracker maintenance, if the bug is still in NEEDINFO status with no change in 30 days the QA team will close the bug as INSUFFICIENTDATA due to lack of needed information. For more information about our NEEDINFO policy please read the wiki located here: https://wiki.documentfoundation.org/QA/Bugzilla/Fields/Status/NEEDINFO If you have already provided the requested information, please mark the bug as UNCONFIRMED so that the QA team knows that the bug is ready to be confirmed. Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-NeedInfo-Ping
Dear Telesto, Please read this message in its entirety before proceeding. Your bug report is being closed as INSUFFICIENTDATA due to inactivity and a lack of information which is needed in order to accurately reproduce and confirm the problem. We encourage you to retest your bug against the latest release. If the issue is still present in the latest stable release, we need the following information (please ignore any that you've already provided): a) Provide details of your system including your operating system and the latest version of LibreOffice that you have confirmed the bug to be present b) Provide easy to reproduce steps – the simpler the better c) Provide any test case(s) which will help us confirm the problem d) Provide screenshots of the problem if you think it might help e) Read all comments and provide any requested information Once all of this is done, please set the bug back to UNCONFIRMED and we will attempt to reproduce the issue. Please do not: a) respond via email b) update the version field in the bug or any of the other details on the top section of our bug tracker Warm Regards, QA Team MassPing-NeedInfo-FollowUp