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.
Product Version = NetBeans IDE Dev (Build 200402151900) Operating System = Linux version 2.4.20-18.9 running on i386 Java; VM; Vendor = 1.5.0-beta2; Java HotSpot(TM) Client VM 1.5.0-beta2-b37; Sun Microsystems Inc. Java Home = /usr/local/java/j2sdk1.5.0/jre System Locale; Encod. = cs_CZ; ISO-8859-2 Home Dir; Current Dir = /usr/local/home/delphym; /usr/local/forte/forte3/NBdev-last/netbeans/bin IDE Install; User Dir = /usr/local/home/delphym/NBdev-last; /usr/local/home/delphym/.netbeans/dev ------------------------------------------------------------------------------- During night my IDE freezed on jdk1.5 beta. When I leaving it it was OK and I didn't use it very heavily. Hope you could recognize something from ThreadDump
Created attachment 13465 [details] FullThreadDump
CC'ing Milan
Dan, don't forget add appropriate keywords, please.
more keywords
Sorry Marian, instead of that I put Milan on CC 'casue I wasn't sure if this deadlock is related to JDK1.5 and hi's interested in such cases
All I can see is that AWT-EventQueue-1 thread is waiting inside repaint of memory meter. Everything other looks idle. Hm.
I reviewed thread dump and I can see no deadlock. Nothing more I can do at this time I guess. Ccing Petr Nejedly and Martin Entlicher in case they'll see more. There are a couple of CVS threads, but it seems to me they're just patiently sleeping. Guys?
hmmm:-/// so why my ide didn't responde? It has all night long time to finish/recover from all task it's been performing? Strange...
btw. how long time did you give your IDE to wake up ?
at least I prepared tea adn eat some cakes :-) 30 min?
VCS threads are sleeping. AWT-EventQueue-1 is strange, I have never seen "waiting on condition" state. But looking into java.awt.Color.darker() there should be nothing to wait for. I have no idea where is the problem. Several thread dumps would hopefully help.
I can't serve, sorry :-|
Looks strange to me. Like if JVM is currently doing some internal bookkeeping (GC, hotspot, ...) and got stuck. Dan, you're great source of strange deadlocks. Please, each time you spot a deadlock, generate _several_ thread dumps (a minute or so apart) and also try to generate a core dump of the JVM process: attach to running JVM: gdb java <pid of the JVM> create a gcode using gdb: gcore It will create a >200MB dump of all JVM data structures. Please try to keep the dumps for individual reports till the issue owner assures you it is "normal java-level deadlock" that needs no gcore investigation. (You can attach reference to this instructions to the issue reports)
Summary: I'm going to close as wontfix. Explanation: Unfortunately we have not enough info to see where the problem could be or to pass this issue to JDK team, although problem seems to be on JDK side. Nothing we can do now. Dan, if you are able to hit such situation again, please follow steps which Petr N. mentioned and reopen with more info. Thx.
OK, I understand and next time, I definitely will order by Peter's instruction. I'm printing them now ot have them always on eyes :-)