https://bugs.kde.org/show_bug.cgi?id=386720
--- Comment #9 from Milian Wolff <m...@milianw.de> --- OK, it's not the hack, it's the sheer amount of errors in my case. I get thousands of ClangProblems (dozens per file, each with up to hundreds of child diagnostics) for a single TU. We should probably limit this somehow and bail out if something goes wrong :-/ What's more: - we add the IncludeFileNotFoundProblem errors to *all* files in the TU. Maybe we should only do that for the main file? This is quite costly. Or we cache the problem pointers - we sometimes get plain garbadge from libclang: https://i.imgur.com/Kd7ZCsS.png I even see this one, which is epic: <somefile> "unused parameter 'frame' [-Wunused-parameter]" child diagnostics: 702 suffice to say, the child diagnostics are bogus like in the screenshot Sigh, let's see how this can be fixed and/or work-arounded :-/ -- You are receiving this mail because: You are watching all bug changes.
