https://bugs.kde.org/show_bug.cgi?id=400222
--- Comment #1 from Jasem Mutlaq <mutla...@ikarustech.com> --- Ok I can confirm this. However, after a LOT of digging around yesterday I wasn't able to locate the leak. I made few changes in GIT to make it better, but when I checked it with tools like heaptrack, I can see FITSView creating (and then destroying) QImage and memory consumption goes back to normal (~120MB), but htop still shows the memory as RES and indeed it doesn't go down even after using delete[] The weird thing as well is that memory allocation itself doesn't seem to increase RES up until the data is _read_ into the array.. not sure what's going on here either. -- You are receiving this mail because: You are watching all bug changes.
