Bug 109609

Summary:	Memory usage spikes when modifying a large .c file, but only when it is first added to a project
Product:	[Applications] kdevelop	Reporter:	Kyle <kleber>
Component:	general	Assignee:	kdevelop-bugs-null
Status:	RESOLVED DUPLICATE
Severity:	normal
Priority:	NOR
Version:	unspecified
Target Milestone:	---
Platform:	Fedora RPMs
OS:	Linux
Latest Commit:		Version Fixed In:

Description Kyle 2005-07-25 22:20:30 UTC

Version:           KDevelop 3.1.2 and 3.1.1 (using KDE KDE 3.3.1)
Installed from:    Fedora RPMs
OS:                Linux

This is similar to bug #96909, except that any modification at all to the file causes KDevelop's memory usage to spike.  Also, the proposed work-around of putting a file named .kdev_ignore in the source code's directory did not have any affect on the memory spikes.  For me, these spikes in memory usage never actually caused Kdeveop to crash, but would cause the computer to page memory to disk for about 30-60 seconds before recovering.  

This problem only surfaced with one particular .c file that is over 6000 lines long.  I tried opening other C++ projects with multiple files and never had a problem.

Comment 1 Jens Dagerbo 2005-07-25 22:31:07 UTC

It's the same basic problem. The C/C++ parser is triggered by the editing of the file and goes to work on it. And consumes a huge amount of memory, sadly.

Dupe.

*** This bug has been marked as a duplicate of 96909 ***