https://bugs.kde.org/show_bug.cgi?id=441543
--- Comment #3 from MIchael Giardino <giard...@bcfmail.com> --- Created attachment 141130 --> https://bugs.kde.org/attachment.cgi?id=141130&action=edit Heaptrack of newly reastarted program This is a heaptrack after the restart, but if I'm reading it correctly it has already leaked a bit in the minute it was running. I can connect it to the process when it begins to really leak, but given the amount of data it generates and how long it takes to trigger, I don't think i can let it run from now until then. Let me know if you can think of something else I can do. heaptrack output will be written to "/home/mikel/Downloads/heaptrack.ksystemstats.121644.gz" injecting heaptrack into application via GDB, this might take some time... injection finished heaptrack stats: allocations: 2680 leaked allocations: 20 temporary allocations: 365 removing heaptrack injection via GDB, this might take some time... ptrace: No such process. No symbol table is loaded. Use the "file" command. The program is not being run. Heaptrack finished! Now run the following to investigate the data: -- You are receiving this mail because: You are watching all bug changes.
