Description: Memory usage build up when pasting image back and forward between sheets (persistent after closing of the document) Steps to Reproduce: 1. Open attachment 144153 [details] 2. Go to sheet 2 3. CMD+A & CMD+X 4. Go to sheet 1 5. CMD+V 6. On Sheet 1 CMD+A & CMD+X 7. Go to sheet 2 & CMD+V 8. Repeat the dance a few times; notice memory usage increasing 9. Close Impress & copy something else to the clipboard Actual Results: Memory usage build-up Expected Results: Memory should be released Reproducible: Always User Profile Reset: No Additional Info: Version: 6.2.0.0.alpha0+ Build ID: c958f52b813d34baa9b5236bb34a08a04e6b0aba CPU threads: 4; OS: Mac OS X 10.12.6; UI render: default; TinderBox: MacOSX-x86_64@49-TDF, Branch:master, Time: 2018-08-10_05:06:44 Locale: nl-NL (nl_NL.UTF-8); Calc: threaded
@Telesto : for some reason, I can't even get your test file to load in my current master build when running an allocation trace.
In fact, I can't get it to load at all, LO just hangs, requiring force kill.
It won't load in Version: 6.1.0.3 Build ID: efb621ed25068d70781dc026f7e9c5187a4decd1 Threads CPU : 4; OS : Mac OS X 10.13.6; UI Render : par défaut; Locale : fr-FR (fr_FR.UTF-8); Calc: group threaded either.
I tried testing this with a brand new 2 slide ODP file. 1) I inserted two graphics from the gallery into slide 2 2) Then Cmd-A in Slide 2 to select all objects, and Cmd-X to cut those objects 3) Switch to Slide 1 and Cmd-V. 4) Repeat in reverse order to cut and paste from Slide 1 to Slide 2. 5) Repeat the whole cycle several times. Persistent memory usage seems to hover around 91.5Mb with Version: 6.2.0.0.alpha0+ Build ID: b8658c0e847afe1ed199c5fa7a2dd5d1d61ccbac CPU threads: 4; OS: Mac OS X 10.13.6; UI render: default; Locale: fr-FR (fr_FR.UTF-8); Calc: threaded No repro really for me, as memory usage seems to remain pretty static. @Telesto : Does it depend on the number / type of objects being cut/paste ?
> @Telesto : Does it depend on the number / type of objects being cut/paste ? Probably, the presentation in question has quite a lot of images. Little more than 1000 on the sheet in question. File is opening fine for me, takes a while though. Version: 6.2.0.0.alpha0+ Build ID: 85818da3307a28b2d9c6fa5c1c97ca7833dfe24c CPU threads: 4; OS: Mac OS X 10.12.6; UI render: default; TinderBox: MacOSX-x86_64@49-TDF, Branch:master, Time: 2018-08-22_04:15:46 Locale: nl-NL (nl_NL.UTF-8); Calc: threaded
This unconfirmed problem happens to me too. Computer: Macbookpro2017 Version: 6.3.0.0.alpha0+ Build ID: 72e204da9a062282e52d5060e7f633e3b21414ff CPU threads: 4; OS: Mac OS X 10.14; UI render: default; VCL: osx; TinderBox: MacOSX-x86_64@49-TDF, Branch:master, Time: 2018-11-26_01:27:57 Locale: zh-CN (zh_Hant.UTF-8); UI-Language: en-US Calc: threaded
(In reply to Alex Thurgood from comment #2) > In fact, I can't get it to load at all, LO just hangs, requiring force kill. Seems like bug 121778
Dear Telesto, 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 https://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
Dear Telesto, 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 https://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://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug