This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.
I don't know what is relevant here... The IDE was up and running for 6 days, in heavy use for about 3 of those. Two large projects were open, both located in one source tree, and they share many files. This morning I applied a patch to the source tree with the IDE still open. I noted that CPU usage was up and found that java was burning 100% - 120% of my dual core CPU. I also noted that the java virtual size was 2GB and the resident set size was 1.6GB. I have 4GB physical mem. The IDE reported that it was parsing the projects, so I let it continue. After parsing reached 100%... and stayed at 100%, I decided to close one of the projects. No change in cpu usage. I tried to generate a thread dump and that's when I discovered that the log was filling with an infinite number of exceptions (log attached below). I then tried closing all documents (no change) and then just restarted the IDE.
Created attachment 79672 [details] log file with continuous exceptions
Created attachment 80892 [details] gdb-cmds for previous comment
Created attachment 80893 [details] messages.log for above comment.
Please ignore the previous two attachements... they were intended for another bug.
Reassigned to component "cnd" (C/C++ native development).
It seems you have a broken NB installation and CND cache. Try to reproduce it in NB 6.7 release. Some of exceptions was fixed. See IZs 160328, 164413.
Quite possible I broke installation. I'm running the version below, and have not seen the issue. I'll refile if it happens again. Closing... Product Version: NetBeans IDE 6.7 RC2 (Build 200906042131) Java: 1.6.0_12; Java HotSpot(TM) 64-Bit Server VM 11.2-b01 System: Linux version 2.6.22.19 running on amd64; UTF-8; en_US (nb) Userdir: /home/toddb/.netbeans/6.7rc2