Summary: | too many resources is used while doing background jobs | ||
---|---|---|---|
Product: | [Applications] kdevelop | Reporter: | Fathi Boudra <fabo> |
Component: | Language Support: CPP (old) | Assignee: | kdevelop-bugs-null |
Status: | RESOLVED WAITINGFORINFO | ||
Severity: | normal | CC: | aleixpol, jonathan.verner, nlovell |
Priority: | NOR | ||
Version: | 4.0.0 | ||
Target Milestone: | --- | ||
Platform: | Debian testing | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: |
Description
Fathi Boudra
2010-07-06 18:27:31 UTC
I'm seeing very high CPU usage from the background parser on *very* large projects. It actually blocks kdevelop from responding for a good while (only happens after I've dropped focus from kdevelop for a while and then try and come back). My temporary workaround is to renice kdevelop after starting it up, which seems to fix the problem. I think that by Background job they mean C++ so assigning to the C++ component. There have been lots and lots of optimizations since 2010. Given that it's so hard to figure out if we can close or not, please reopen with a more specific complaint, if it still applies. Thank you for the bug report. As this report hasn't seen any changes in 5 years or more, we ask if you can please confirm that the issue still persists. If this bug is no longer persisting or relevant please change the status to resolved. |