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

List:       kdevelop-bugs
Subject:    [Bug 109833] New: Parsing special C++ header file lets kdevelop eat up all RAM & get killed
From:       kdevelop-bugs-admin () barney ! cs ! uni-potsdam ! de
Date:       2005-07-29 12:44:30
Message-ID: 20050729144427.109833.doll () tm ! uka ! de
[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=109833         
           Summary: Parsing special C++ header file lets kdevelop eat up all
                    RAM & get killed
           Product: kdevelop
           Version: 3.2.2
          Platform: unspecified
        OS/Version: Linux
            Status: UNCONFIRMED
          Severity: crash
          Priority: NOR
         Component: general
        AssignedTo: kdevelop-bugs kdevelop org
        ReportedBy: doll tm uka de


Version:           3.2.2 (using KDE 3.4.2, Kubuntu Package 4:3.4.2-0ubuntu0hoary1 )
Compiler:          gcc version 3.3.5 (Debian 1:3.3.5-8ubuntu2)
OS:                Linux (i686) release 2.6.10-5-386

Kdevelop consumes too much RAM when importing the C++ header file \
~/libxorp/callback_debug.hh from the XORP 1.1 release \
(http://xorp.org/downloads.html) into a project (Menu Project->Import). It seems that \
kdevelop does not crash, but it consumes so much RAM when importing header files with \
many template parameters, that it eats up all RAM of a "normal PC",  which "only" \
have a few GiB of RAM.

This header file is generated with the pyhton script ~/libxorp/callback-gen.py (see \
comment at the top of the file):

python callback-gen-py -d -b 6 -l 15 > callback_debug.hh

kdevelop has no problems opening/highlighting the file without import into a project, \
nor has it problems with the non-debug version ~/libxorp/callback_nodebug.hh, \
(generated as above, but without option -d).

I've played a bit with the generator script. On my notebook (Pentium M 2 GHz, 1 GiB \
RAM, 2 GiB swap) I was able to import a header file generated with parameters up to \
b=l=6, or up to b=2 and l=16, which both consume about 2 GiB of virtual RAM during \
parsing. It took e few minutes to parse the file. After parsing, the memory \
consuption falls back to normal levels (about 150 MiB).


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