Bug 377389

Summary:	background parser hogs memory and CPU while working with git
Product:	[Applications] kdevelop	Reporter:	Be <be.0>
Component:	Code completion	Assignee:	kdevelop-bugs-null
Status:	RESOLVED WORKSFORME
Severity:	normal	CC:	master.haber
Priority:	NOR
Version First Reported In:	5.0.3
Target Milestone:	---
Platform:	Other
OS:	Linux
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:

Description Be 2017-03-08 15:38:43 UTC

The background parser automatically starts as soon as I switch git branches. This makes it difficult to work with git while KDevelop is open. For example, when switching to another branch then merging a branch into that, the background parser will have to parse the project twice, but I only need it to run after I am done with a series of git operations. Stopping the background parsing after each step is not practical, as it slows down my system dramatically as soon as the background parser starts. I can think of two workarounds:

1. Add an action to KDevelop to suspend/resume background parsing that could be bound to a global keyboard shortcut. This would require the user to remember to use it before starting to work with git.
2. Add an optional timer to delay the start of the background parser. However, this could get annoying when all that the user needs to do is switch to a different branch.

Related:
https://bugs.kde.org/show_bug.cgi?id=241032

Comment 1 Ian H 2017-03-08 18:01:32 UTC

i've never seen it be a real issue with processing power, but i have a bunch of cores. The biggest issue i've seen with switching git branches is that it fucks up the parser and everything gets parsed wrong.

Comment 2 Be 2017-03-08 18:02:57 UTC

I'm using an old Intel Core i5 2410M with 4GB of RAM.

Comment 3 Ian H 2017-03-08 18:04:29 UTC

Ah, that might do it. 
It does have to re-parse every file that changed though, which could end up being the equivalent of reparsing the entire project.  

There is an option that lets you turn down the number of processes it uses at a given time, so that might be an option for you to change it to one process, so it wont use all of your cpu.

Comment 4 Justin Zobel 2022-11-03 01:40:28 UTC

Thank you for reporting this issue in KDE software. As it has been a while since this issue was reported, can we please ask you to see if you can reproduce the issue with a recent software version?

If you can reproduce the issue, please change the status to "REPORTED" when replying. Thank you!

Comment 5 Bug Janitor Service 2022-11-18 05:15:40 UTC

Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!

Comment 6 Bug Janitor Service 2022-12-03 05:19:34 UTC

This bug has been in NEEDSINFO status with no change for at least
30 days. The bug is now closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!