https://bugs.kde.org/show_bug.cgi?id=384953
--- Comment #2 from Daniel Santos <daniel.san...@pobox.com> --- (In reply to Sven Brauch from comment #1) > Are you, by any chance, out of memory? Sorry for my slow response. As I said, there was very little I/O at the time and iirc, I had a few hundred MiB in swap that had been there for days (probably from garbage sitting in /tmp). I was able to look over at my computer and see that the HDD light was not coming on. This is what indicated to me that this was some type of locking issue. I do not wish to lower the number of parsing threads below the number of CPU cores that I have and I refuse to believe that the kernel could *possibly* do such a horrible job as scheduling that a UI thread would be completely starved for an entire 20 seconds. I have already excluded areas of the GCC project that I'm not working on (in addition to testsuites as they will crash clang). That being said, parsing a file with 25k lines like gcc/config/i386/i386.c takes quite a long time. Of course, that shouldn't be a reason for the UI to not respond for that duration. I'll try to reproduce this later this week and see if I can discover any other helpful details. -- You are receiving this mail because: You are watching all bug changes.
