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.
Summary: | The IDE hangs whilst in the middle of editing a file, cpu goes to 99% and ends up with having to kill the process. | ||
---|---|---|---|
Product: | editor | Reporter: | petermount <petermount> |
Component: | Hints & Annotations | Assignee: | issues@editor <issues> |
Status: | RESOLVED INCOMPLETE | ||
Severity: | normal | Keywords: | RANDOM, THREAD |
Priority: | P3 | ||
Version: | 6.x | ||
Hardware: | Macintosh (x86) | ||
OS: | Mac OS X | ||
Issue Type: | DEFECT | Exception Reporter: | |
Attachments: |
The netbeans log of the session up until the crash
Thread dump of NetBeans 6.9 whilst locked |
Description
petermount
2010-06-23 11:24:29 UTC
Created attachment 100358 [details]
The netbeans log of the session up until the crash
Could you please take and attach thread dump while you run into this? Thanks. http://wiki.netbeans.org/GenerateThreadDump Created attachment 100421 [details]
Thread dump of NetBeans 6.9 whilst locked
Ok here's a thread dump as I've managed to get it to hang again.
This time it was while creating a new class and running auto import
This is strange. The thread dump shows that the only thread with some activity is AWT-EventQueue-1, but it's not blocked. At the time of taking the threaddump it was rendering the editor error stripe. No other threads seem to do anything. In the log file there is an exception from maven, but it's probably unrelated. Could you please generate more threaddumps (eg. several consecutive dumps in approx 1s succession)? Thanks Up until that last thread dump it was happening every few days, however it's not done it since - although it has had several real go-slows which I thought was the same, but it then recovered. I had a look at the dump myself and couldn't see anything either. If it happens again then I'll do another dump. One thing I have observed however, you mentioned maven - I use maven exclusively and a lot of the go-slows do happen just after a maven build. Some of my maven builds are pretty big so that may not necessarily be unrelated after all. |