Description: ReleasePoolHolder() doesn't completely release all objects held in memory leading to gradual increase in memory consumption Steps to Reproduce: 1. Open Writer document 2. Open "Find" dialog 3. Close "Find" dialog 4. Repeat step 3 multiple times Actual Results: Ref count shows that not all memory released Expected Results: Memory should be released correctly Reproducible: Always User Profile Reset: No Additional Info: Instruments.app points (OSX memory profiler) points to line 41 in saltimer.h : ~ReleasePoolHolder() { [mpPool release]; } User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:54.0) Gecko/20100101 Firefox/54.0
Created attachment 135789 [details] Refcount cycle screenshot The screenshot shows the refcount cycle for ReleasePool
No idea why the count suddenly jumps from 1 back up to 2 when it is supposed to be decrementing...
Jan-Marek: having noticed your commit in saltimer history, thought you might be interested in this one.
Confirming with 5.4.1.1
** Please read this message in its entirety before responding ** To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from http://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug
Not seeing this anymore with current master build.