https://bugs.kde.org/show_bug.cgi?id=372040
--- Comment #11 from RJVB <rjvber...@gmail.com> --- Created attachment 103447 --> https://bugs.kde.org/attachment.cgi?id=103447&action=edit workaround patch (In reply to Kevin Funk from comment #10) > *** Bug 362037 has been marked as a duplicate of this bug. *** But but but ... this is a duplicate of my older 362037 :) But yes, this is mostly caused by clang FixIts, but missing includes that lead to significant IO aren't the only problem. I get similar lock-ups for just about any problem for which a fix might be found, like undefined variables. That also leads to a call of `scanIncludePaths()`. I only see this on Mac though, *much* less on my otherwise significantly slower Linux rig (both have spinning disks). Whatever the exact cause, the underlying problem here is that the operation is done on the main (UI) thread. The workaround patch makes the situation liveable. If there were a way to be certain events were processed it would probably (almost) be acceptable: when events are processed that stem from user activity this is good indication that the user isn't interested in seeing a proposed fix. For instance because s/he is already fixing the issue. In fact, I do find the fix-it and similar pop-ups often rather intrusive and bordering on the annoying. Other times I see a pink/red line and have a hard time getting a popup that tells me what's wrong. -- You are receiving this mail because: You are watching all bug changes.
