[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kdevelop-bugs
Subject:    [Bug 109609] New: Memory usage spikes when modifying a large .c file, but only when it is first adde
From:       kdevelop-bugs-admin () barney ! cs ! uni-potsdam ! de
Date:       2005-07-25 20:20:32
Message-ID: 20050725222029.109609.kleber () fastemail ! us
[Download RAW message or body]

------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
         
http://bugs.kde.org/show_bug.cgi?id=109609         
           Summary: Memory usage spikes when modifying a large .c file, but
                    only when it is first added to a project
           Product: kdevelop
           Version: unspecified
          Platform: Fedora RPMs
        OS/Version: Linux
            Status: UNCONFIRMED
          Severity: normal
          Priority: NOR
         Component: general
        AssignedTo: kdevelop-bugs kdevelop org
        ReportedBy: kleber fastemail us


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.


[prev in list] [next in list] [prev in thread] [next in thread]