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 115482 [details] thread dump Does not recover, has to be killed.
Please, it would be helpful to know more - what were you doing just before it froze ? Is there any particular action you took that resulted in this ? As the thread dump indicates waits in debugger, I am asking Martin for help with evaluation. Martin, is this possibly within your scope ?
I did not find any indication that this would be a debugger issue. AWT-EventQueue thread is missing at all. It had to somehow crash on some sever error that it did not recover. This it the reason why the GUI is stuck and does not recover. Please provide the messages.log file, that should contain some errors.
Created attachment 115495 [details] Log files I think I was indeed debugging, but possibly there was a long idle time after my last activity and the crash/lockup.
The logs suggest problems related to WebServices. Reassigning for further evaluation.
There has been quite a lot of ugly behaviour in 7.1 after extended use like eight hours or so. In addition to OutOfMemoryError, I have noticed one second delays with tree navigation one node at the time in the Projects window, and 100% CPU use for no obvious reason just after the IDE was idle in the background. I have tried jvisualvm to get a snapshot, but then both the IDE AND jvisualvm stopped responding, so I don't really know how to help.
webservices seems to be just part of path in the log, there are no exceptions/warning etc with websvc. unfortunately last activity was more then a year ago, if it's still valid we can try to reevaluate the issue. project sample may help if it's possible to attach. in some cases the reason may be low default value for memory allocation, especially for debug etc. in this case memory increase in netbeans.conf should solve the issue, in case of some memory leak or a problem unrelated with memory it will just delay the issue. Please reopen with more details (project or new dump if possible etc) if it still have sense. There is no enough information so far.