https://bugs.kde.org/show_bug.cgi?id=379551
--- Comment #24 from Martin Fuhrer <mfuh...@alumni.ucalgary.ca> --- I have been testing the KDevelop 5.2.1 AppImage on Debian 7.8 (wheezy) for the last few weeks (our office is still using KDevelop 4.7.4, which runs great, albeit a bit slow with large projects, and it would be nice to move to the latest). For the most part, KDevelop 5.2.1 is runs along with no problems (sometimes for one to two days at a time), but occasionally it starts eating away at memory rapidly, to the point where my desktop starts freezing up and I have to type Ctrl-Alt-F1 to switch to console mode and kill the kdevelop process. My workstation has 32 GB RAM, and after I kill the process, usually 20 GB or more becomes available again. The last few days I have been launching KDevelop with the latest heaptrack (built from master). Rather than launching the AppRun script, I simply set the environment variables from my shell (csh), and launch KDevelop with: heaptrack kdevelop >& kdevelop_log.txt This afternoon I encountered the memory leak once again. Managed to select Session > Quit from KDevelop, and though the window disappeared, the kdevelop process (PID 12200) kept running and consuming additional memory. Eventually I sent two SIGTERM signals to kill it. I have attached the heaptrack file and the first and last 1000 lines of the log file. Hopefully there is some helpful information here. -- You are receiving this mail because: You are watching all bug changes.
