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.
Created attachment 127348 [details] Profiler snapshot Product Version: NetBeans IDE Dev (Build 201211060001) Java: 1.7.0_09; Java HotSpot(TM) 64-Bit Server VM 23.5-b02 Runtime: Java(TM) SE Runtime Environment 1.7.0_09-b05 System: Windows 7 version 6.1 running on amd64; Cp1252; en_CA (nb) User directory: C:\Users\Gili\AppData\Roaming\NetBeans\dev Cache directory: C:\Users\Gili\AppData\Local\NetBeans\Cache\dev Every once in a while (say within 30 minutes of launching Netbeans) it goes into a bad state where it begins using 100% cpu, across all cores. It's not clear what it's doing (it's not obvious what triggers it and there is no UI indicating any activity). Often this problem continues even after Netbeans is shut down (The task netbeans64.exe kills running indefinitely and must be killed). I generated a self-profile snapshot generated from within Netbeans. Please let me know if this helps and/or whether you are able to reproduce this yourself.
Snapshot, you attached to this bug, shows no activity. Can you try it once more and attach npss file (instead of nps). .npss file is created in Windows TEMP directory and is named selfsamper<number>.npss. Please also attach messages.log file. Thanks.
Created attachment 127539 [details] Thread-dump of process that fails to shut down I no longer seem to get the 100% cpu usage issue, but the process still fails to shutdown cleanly so I'll focus on that instead. Here is a thread-dump of Netbeans after the GUI shut down but the process remains.
(In reply to comment #2) > Created attachment 127539 [details] > Thread-dump of process that fails to shut down This is duplicate of issue #221034. > I no longer seem to get the 100% cpu usage issue, OK, I am closing this report. > but the process still fails > to shutdown cleanly so I'll focus on that instead. Here is a thread-dump of > Netbeans after the GUI shut down but the process remains. .. but this deadlock is completely unrelated to the original problem with 100% cpu usage. Next time please file new issue in such situation. Thanks.