Version: 3.5.5 (using 3.5.10 "release 61" , openSUSE ) Compiler: Target: x86_64-suse-linux OS: Linux (x86_64) release 2.6.27.29-0.1-default Often, when I open a C++ file in Kdevelop after opening my custom makefiles project (~10000 files), and do nothing else kdevelop starts consuming 70-90% of CPU and begins to exhaust available virtual memory (e.g. I just killed it after its memory image grew to 3Gb in less than a minute, and it was growing even more. GDB stack trace attached: (gdb) bt #0 0x00007fd4ea570c93 in free () from /lib64/libc.so.6 #1 0x00007fd49b941750 in ?? () #2 0x00007fd49b941750 in ?? () #3 0x00007fd49b93b380 in ?? () #4 0x00007fd4dcf7441c in QMapPrivate<QString, KSharedPtr<FileModel> >::clear () from /opt/kde3/lib64/kde3/libkdevcppsupport.so #5 0x00007fd4dcf7441c in QMapPrivate<QString, KSharedPtr<FileModel> >::clear () from /opt/kde3/lib64/kde3/libkdevcppsupport.so #6 0x00007fd4dcfc5fba in StoreWalker::~StoreWalker () from /opt/kde3/lib64/kde3/libkdevcppsupport.so #7 0x00007fd4dcf67a1a in CppSupportPart::parseEmit () from /opt/kde3/lib64/kde3/libkdevcppsupport.so #8 0x00007fd4dcf689aa in CppSupportPart::customEvent () from /opt/kde3/lib64/kde3/libkdevcppsupport.so #9 0x00007fd4eaed9201 in QObject::event () from /usr/lib/qt3/lib64/libqt-mt.so.3 #10 0x00007fd4eae7a755 in QApplication::internalNotify () from /usr/lib/qt3/lib64/libqt-mt.so.3 #11 0x00007fd4eae7b53a in QApplication::notify () from /usr/lib/qt3/lib64/libqt-mt.so.3 #12 0x00007fd4eba13e92 in KApplication::notify () from /opt/kde3/lib64/libkdecore.so.4 #13 0x00007fd4eae7c599 in QApplication::sendPostedEvents () from /usr/lib/qt3/lib64/libqt-mt.so.3 #14 0x00007fd4eae2a805 in QEventLoop::processEvents () from /usr/lib/qt3/lib64/libqt-mt.so.3 #15 0x00007fd4eae912e9 in QEventLoop::enterLoop () from /usr/lib/qt3/lib64/libqt-mt.so.3 #16 0x00007fd4eae91172 in QEventLoop::exec () from /usr/lib/qt3/lib64/libqt-mt.so.3 #17 0x0000000000407a6d in ?? () #18 0x00007fd4ea519586 in __libc_start_main () from /lib64/libc.so.6 #19 0x00000000004072e9 in ?? () #20 0x00007ffffd2e6478 in ?? () #21 0x000000000000001c in ?? () #22 0x0000000000000001 in ?? () #23 0x00007ffffd2e7f54 in ?? () #24 0x0000000000000000 in ?? () (gdb) quit
Sorry, but imo this bugreport is totally useless: - kdevelop does require time and resources to parse such huge projects, you might want to disable full-project-parsing - there's nothing wrong with consuming available memory, if required - the bt is totally useless
And additionally to that we're not fixing KDevelop3 anymore.
Created attachment 37264 [details] Improved stacktrace
Re #1: All parsing options are off as they have never worked reliably anyway. Only word completion from the currently opened document is enabled. Anyway, I've attached a hopefully better stack trace.
(In reply to comment #4) > Re #1: All parsing options are off as they have never worked reliably anyway. > Only word completion from the currently opened document is enabled. Anyway, > I've attached a hopefully better stack trace. Well, its a completely different one. And you can't turn off parsing of C++ files either. Anyway, as I said no work is going into kdevelop3, so this won't be fixed.