https://bugs.kde.org/show_bug.cgi?id=518020
--- Comment #11 from Harald Sitter <[email protected]> --- Mind that you need to start heaptrack before the leak begins. Doing it after the memory is already leaked will not produce useful data. -- You are receiving this mail because: You are watching all bug changes.
