https://bugs.kde.org/show_bug.cgi?id=368855
--- Comment #8 from Rolf Eike Beer <k...@opensource.sf-tec.de> --- > The time is spent in libclang, i.e. parsing. This behaviour seems > perfectly > normal to me; files changed, they have to be reparsed, that takes a > while. So, > not a bug ...? There are few files, and parsing a few thousand lines of codes shouldn't take half a minute on a Core i7. In fact this sometimes works fine (and fast), so I guess the problem really is that the files changed while libclang is trying to parse them. -- You are receiving this mail because: You are watching all bug changes.
