https://bugs.kde.org/show_bug.cgi?id=379669
--- Comment #23 from RJVB <rjvber...@gmail.com> --- > Maybe your other crashes with "project unloading" were also related to > unloaded language plugins. Which language plugins do you use? Possibly, but I cannot remember if I had any "interesting" terminal output at the time and haven't seen them for a while (thanks to my patch?). The big problem with this issue is that it appears to happen at random (the timeouts in certain operations may be responsible for that). That makes debugging it so tricky (and you really need to build without any optimisation, which is not an option for me for everyday use - which is how I use KDevelop...) I mostly work with C, C++ and ObjC(++) files, CMake files and the occasional Python file. But I've never taken stock exactly which language plugins get installed with KDevelop. I have a hunch (but no proof) that the dangling data that remains is only a single item at the time, not a whole tree, so the impact on subsequent sessions could be negligible. But I guess that impact could be made 0 by marking the duchain cache as dirty if the cleanup knowingly leaves dangling data, so that the whole cache gets rebuild during the next startup? -- You are receiving this mail because: You are watching all bug changes.
