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

List:       kde-bugs-dist
Subject:    [Bug 147741] Kdevelop huge memory consumption
From:       David Nolden <david.nolden.kdevelop () art-master ! de>
Date:       2007-10-12 15:29:48
Message-ID: 20071012152948.3837.qmail () ktown ! kde ! org
[Download RAW message or body]

------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
         
http://bugs.kde.org/show_bug.cgi?id=147741         




------- Additional Comments From david.nolden.kdevelop art-master de  2007-10-12 \
17:29 ------- The problem here is that kdevelop parses all files in the current \
project and keeps the result in memory.

So you simply cannot use it with big projects like the whole kernel. The solution \
would be either disabling the parsing, or creating a project an the smaller subtree \
of the kernel you're actually working on.

Also there is options in the C++ support project configuration that significantly \
influence memory-consumption, make sure to check "Do not preprocess included headers" \
there.

About the valgrind-output:
It doesn't seem to report any leakages.


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