Bug 243780 - too many resources is used while doing background jobs
Summary: too many resources is used while doing background jobs
Status: RESOLVED WAITINGFORINFO
Alias: None
Product: kdevelop
Classification: Applications
Component: Language Support: CPP (old) (show other bugs)
Version: 4.0.0
Platform: Debian testing Linux
: NOR normal
Target Milestone: ---
Assignee: kdevelop-bugs-null
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-07-06 18:27 UTC by Fathi Boudra
Modified: 2021-12-03 22:14 UTC (History)
3 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Fathi Boudra 2010-07-06 18:27:31 UTC
Version:           4.0.0 (using KDE 4.4.4) 
OS:                Linux

This a forwarded Debian bug report:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=587502

About week ago I had several minor updates in Qt libs. After this update
background jobs is "eating" all recources of my PC(I have AMD Athlon(tm) 64 X2
5200+, 1,8G RAM). While this problem is happend, kdevelop use all available
RAM, after than it use big piece if swap. During this time i see strong
hard disk activity.
Step to reproduce:
Import some CMake based project
Wait until start background jobs(I think this is project sources indexing)
Look for RAM/HDD usage and activity.

Also I would say project tree have cross symlinks inside.
Also as I can see kdevelop can not eat more than 1,8-2G RAM (I see this on
another PC with Intel C2D, 4G RAM inside)


Reproducible: Didn't try

Steps to Reproduce:
> Please, give me complete and exact steps to reproduce.
1. get sources from http://rtmpd.com/changeset/1424/branches/0.1?old_path=%2F&format=zip
2. cd builders/cmake
3. cmake . && make
4. run Kdevelop4
5. import cmake project from builders/cmake
6. open some source files (for running background jobs, i think this is 
indexing of source files for highlight and code completion)
Comment 1 nlovell 2010-07-23 21:22:56 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.
Comment 2 Aleix Pol 2010-12-21 01:20:07 UTC
I think that by Background job they mean C++ so assigning to the C++ component.
Comment 3 Aleix Pol 2013-02-27 23:46:06 UTC
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.
Comment 4 Justin Zobel 2021-03-09 22:48:04 UTC
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.