https://bugs.kde.org/show_bug.cgi?id=372040
--- Comment #6 from Sven Brauch <m...@svenbrauch.de> --- Ok, so it really seems to be I/O. Thanks for the tests! Maybe it would be useful after all to run kdevelop in gdb, interrupt it when it's hanging, and get a backtrace. I guess that's the easiest way to find the code path causing the I/O -- I can't see it from the perf data. -- You are receiving this mail because: You are watching all bug changes.
