https://bugs.kde.org/show_bug.cgi?id=368838
--- Comment #113 from Matt Whitlock <k...@mattwhitlock.name> --- (In reply to David Edmundson from comment #112) > @Matt > How can you tell what is leaking from looking at comment #0? There have been at least two distinct memory leaks discussed in this thread. The original report by Antonio Orefice is about a memory leak that occurs when Plasma renders images. Antonio posted a link to a video demonstrating the leak in Comment #59. I am able to reproduce his leak by the same method: force Plasma to paint a lot of images in a short amount of time. It will also leak just the same eventually in normal use, but it takes longer. The leak occurs even without opening the "Add Widget" panel and scrolling the list up and down like mad, but that's one quick way to reproduce it. The other leak was due to the logic error that you described in Comment #86. That leak has been fixed by https://codereview.qt-project.org/#/c/202781/. > and what do you mean by an "in-process leak". All leaks are in-process. Firstly, that's not true; it's entirely possible to leak pixmaps, and those are in the X server's process, not the X client's. But in this case, what I meant was that the leak that was fixed by calling endSync() was a leak of graphics memory, not a leak of system memory, so it wasn't accounted to the plasmashell process. -- You are receiving this mail because: You are watching all bug changes.
