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

List:       kdevelop-bugs
Subject:    [Bug 144891] New: kdevvelop using excessive memory when importing PHP
From:       aaronw () net ! com
Date:       2007-04-30 19:26:32
Message-ID: 20070430212631.144891.aaronw () net ! com
[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=144891         
           Summary: kdevvelop using  excessive memory when importing PHP
                    5.2.1 as a standard C application with custom makefiles
           Product: kdevelop
           Version: unspecified
          Platform: unspecified
        OS/Version: Linux
            Status: UNCONFIRMED
          Severity: normal
          Priority: NOR
         Component: Language Support: CPP
        AssignedTo: kdevelop-bugs kdevelop org
        ReportedBy: aaronw net com


Version:           unknown (using KDE 3.5.6 "release 64.1" , openSUSE )
Compiler:          Target: x86_64-suse-linux
OS:                Linux (x86_64) release 2.6.18.8-0.1-default

When I attempted to import php 5.2.1 as an existing project with the project type \
Generic C Application (Custom Makefiles) Kdevelop consumes an excessive amount of \
memory. I saw it hit over 5GB of virtual memory while importing with 1.6GB resident \
then it dropped down to around 380MB after it finished.  My computer is a 3.2GHz \
Pentium 4 with 2GB of RAM.  The computer was quite sluggish and paging like crazy, \
with top showing wait consistently over 90%.

After I imported the project and the memory dropped back down, just opening the \
project import dialog caused the memory usage to shoot up to 2.7GB.

After I quit KDevelop and restarted it and re-opened the project memory usage is \
around 380MB.

For the most part this is the standard PHP with the PAM extension added, however \
configure, libtool, the Makefile and php_config.h were edited since the target is an \
embedded system requiring cross compilation.  I am not using KDevelop for building \
but only for editing, ctags and grep.

This is repeatable since I gave up the first time I tried importing and killed \
kdevelop partway through.  The second time I decided to let it grind away and it \
eventually finished.


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

Configure | About | News | Add a list | Sponsored by KoreLogic