I've been using kdevelop5 to develop some backend applications in Python, but lately kdevelop5 has been giving me grief. I'm curious if anyone else out there is experiencing anything similar.

I open the app and not long after I get started, the disk activity light on the front of my machine lights up solid and the entire system becomes unresponsive (virtually frozen). If I'm able to pull up the KDE system activity monitor (which is rarely successful when this is happening), it shows kdevelop utilizing more and more memory which ultimately leads to swapping all that excess memory usage to disk. If I'm able to kill KDevelop, the system becomes responsive again.

With all that said, I started invoking kdevelop from the command line via timeout and strace (e.g.

Code: Select all

timeout 60 strace kdevelop

) so that strace could report some valuable info, but that kdevelop would eventually be closed (forcibly) after 60 seconds so that I'd regain control of my system.

I couldn't find anything consistent other than the app seemed to be performing some kind of event polling when the system would essentially freeze. Once the app was closed, the HDD activity would stop and the system would snap back to being functional once again.

Any thoughts? I'd like to continue using it. I'm currently using KATE but I would like to give the projects and git commit features a go in Kdevelop.

Thanks,

Try removing ~/.cache/kdevduchain for a start.

If that doesn't fix it, maybe there's a bug in one of the language plugins which makes it hang on your code. Maybe you can attach a debugger while it hangs and obtain a backtrace?