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.
[ BUILD # : 200909211401 ] [ JDK VERSION : 1.6.* ] After installing 200909211401, launching it, adding 2 ruby projects, then closing the IDE, I reopened 200909211401 and when the IDE started scanning my projects, both CPUs in my machine pegged at 100% with over 99% being allocated to NetBeans. This was not the case in 200909200201 with the same 2 projects.
Created attachment 88068 [details] Messages Log from first invocation where noticed.
Created attachment 88069 [details] Initial Profiler Trace (just after CPUs hit 100%)
Created attachment 88070 [details] Profiler Trace from middle of 100% CPU utilization.
Created attachment 88071 [details] Profiler Trace of end of 100% CPU utilization
Created attachment 88072 [details] Profile Trace from after CPU dropped to normal usage following project scanning.
Looking at the profiler traces indicates a huge percentage of time spent in Object.wait which indicates some level of resource starvation or locking.
Could you please attach those snapshots as .nps files, it doesn't appear to be possible to import .xml files into the IDE (which seems a bit silly since exporting to .xml is possible - I filed #172752 for that).
Unfortunately, I only have them as XML files.
Created attachment 88811 [details] snapshot.nps
The initial project scan for our project have reverted back to the 6.5beta performance of an hour or so for the initial scann
Hi Nigel, can you please file a new issue against java for your snapshot, this issue is for Ruby (in your snapshot the time is spent in indexing java sources, a different problem than Eric's). Thanks.
created bug#173720
Are you still seeing this? If yes, can you please take .nps snapshots and attach them here? (Unfortunately there still isn't a way to import .xml snapshots and trying to figure out the culprit from plain xml is a bit painful).