https://bugs.documentfoundation.org/show_bug.cgi?id=140045
--- Comment #8 from [email protected] --- Created attachment 175622 --> https://bugs.documentfoundation.org/attachment.cgi?id=175622&action=edit screenshots showing Windows memory usage A compilation of several screenshots of Windows Task Manager showing memory allotment after 0, 20, 40, 60, 80, and 100 replacements of Telesto's sample PNG file in a brand new LO Draw document created with: Version: 7.3.0.0.alpha0+ (x64) / LibreOffice Community Build ID: 21b2c6b7d8f4661dcbd40df4f8b9126d331cbd7f CPU threads: 8; OS: Windows 10.0 Build 19043; UI render: Skia/Vulkan; VCL: win Locale: en-US (en_US); UI: en-US Calc: CL with the document's page dimensions set to 42.66″ x 21.33″ inches, which produces an exported PNG 4096 x 2048 pixels (which is proportional to the dimensions of Telesto's sample image). Shown in this attachment, notice that the memory consumption progressed from 447.3MB starting with 0 replacements ending at 2,178.0MB after 100 replacements, resulting in an almost five-fold increase (4.8 times) the memory consumption in less than 10 minutes. The only delay during testing was time taken to screenshot Task Manager. Other than that, it was just a rapid image replacement, one after another, saving after every 20 replacements. While this attachment shows the memory leak created using the image replacement function, I did NOT see a notable degradation in performance as far as speed (saving the document) goes. That tells me that the speed degradation may be a problem with either the brevity of this test, in that it doesn't approach my typical real-world usage of the program in both number of replacements (think 30+ pages in a Draw document, each having 2 or images, and me spending lots of time replacing them while I audition images for the best possible composition of the final image) or the actual number of replacements over time -- or --- just to throw a wrench into things, in a real-world situation I'm also heavily editing text captions as I pull in each picture (so the caption matches the content of the image). Regardless of the reason for the degradation of speed over time, usually manifesting itself in how long it takes the document to save (despite that the actual number of pages / images the document contains might not have changed throughout the course of working with the document) this test at least serves to demonstrate the memory leak. -- You are receiving this mail because: You are the assignee for the bug.
