https://bugs.documentfoundation.org/show_bug.cgi?id=140045
--- Comment #15 from [email protected] --- (In reply to Julien Nabet from comment #14) > Yep using small png to show memleak could be useful because tools like > Valgrind are very slow. So with an image of 127MB, it's too long. 40 replacements of a 528 x 738 32-bit PNG file (one of my standards) went from 215MB initial memory allotment to 355MB, 1.6 times initial, and additional memory is consumed per save at about the same rate (1-2MB per save) as the previous test. So the leak is there, possibly two, but I have 32GB of ram in this box, so the other issue -- whatever is slowing me down over time -- I don't believe is this leak. I'm prepared to speculate what's causing the performance degradation over time, but haven't tested my idea and I don't want to distract from this bug report. -- You are receiving this mail because: You are the assignee for the bug.
