https://bugs.kde.org/show_bug.cgi?id=369374
Kevin Funk changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
Latest Commit|
https://bugs.kde.org/show_bug.cgi?id=369374
--- Comment #8 from Kevin Funk ---
@Wei-Cheng: Want to get started hacking on KDevelop? Looks like you're almost
there. :)
Patches welcome! See https://www.kdevelop.org/contribute-kdevelop
--
You are receiving this mail because:
You
https://bugs.kde.org/show_bug.cgi?id=369374
--- Comment #7 from Wei-Cheng Pan ---
It's KDevelop::BackgroundParser::parseComplete emitting the signal.
We'll need to add a timer to update the progress bar, instead of notify the
main thread in every single step.
--
You are
https://bugs.kde.org/show_bug.cgi?id=369374
--- Comment #6 from Wei-Cheng Pan ---
Created attachment 101637
--> https://bugs.kde.org/attachment.cgi?id=101637=edit
another hotspot
This report was measured after I commented out the line I mentioned before.
Looks like
https://bugs.kde.org/show_bug.cgi?id=369374
KiloAlphaIndia changed:
What|Removed |Added
CC||k...@stierand.com
---
https://bugs.kde.org/show_bug.cgi?id=369374
--- Comment #4 from Wei-Cheng Pan ---
I commented out this line:
m_parser->updateProgressBar();
in
KDevelop::BackgroundParserPrivate::parseDocumentsInternal
and the GUI thread becomes idle and works normally.
Maybe we can
https://bugs.kde.org/show_bug.cgi?id=369374
Wei-Cheng Pan changed:
What|Removed |Added
Attachment #101341|0 |1
is obsolete|
https://bugs.kde.org/show_bug.cgi?id=369374
--- Comment #2 from Wei-Cheng Pan ---
Created attachment 101341
--> https://bugs.kde.org/attachment.cgi?id=101341=edit
perf result after it start parsing C++ files
--
You are receiving this mail because:
You are watching all
https://bugs.kde.org/show_bug.cgi?id=369374
--- Comment #1 from Milian Wolff ---
The short living threads are used by libclang for crash resilience. You can
verify whether that really is the problem by temporarily disabling that
feature. For that, you will need to recompile