https://bugs.kde.org/show_bug.cgi?id=369573
--- Comment #15 from Milian Wolff <m...@milianw.de> --- Thanks, can you install debug information for kdevelop and rerun heaptrack please? Many interesting locations could not be resolved in your trace. We now only know that /something/ in kdevqmljs seems to run Path::cd repeatedly, apparently leading to an ever increasing path that eventually consumes all memory. The question now is what part of our code base is triggering this, and why. -- You are receiving this mail because: You are watching all bug changes.
