https://bugs.kde.org/show_bug.cgi?id=367893
--- Comment #4 from Milian Wolff <m...@milianw.de> --- Oh, and you could also try out heaptrack with the project you can reproduce the issue with: heaptrack kdevelop -s ... # wait a few seconds while verifying that the process is actually exhibiting the bad behavior # ctrl + C to quit, alternatively use `ulimit -v` to set some limit on the virtual memory to prevent # it from taking down your other applications then send us the heaptrack.gz data file, e.g. upload it here -- You are receiving this mail because: You are watching all bug changes.
