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.

Bug 144424

Summary:	NB froze at deadlock detection
Product:	debugger	Reporter:	Petr Cyhelsky <cyhelsky>
Component:	Java	Assignee:	issues@debugger <issues>
Status:	CLOSED INVALID
Severity:	blocker	Keywords:	RANDOM
Priority:	P4
Version:	6.x
Hardware:	Macintosh
OS:	Mac OS X
Issue Type:	DEFECT	Exception Reporter:
Attachments:	messages.log

Description Petr Cyhelsky 2008-08-19 17:56:59 UTC

Product Version: NetBeans IDE Dev (Build 200808190201)
Java: 1.5.0_13; Java HotSpot(TM) Client VM 1.5.0_13-120
System: Mac OS X version 10.4.11 running on i386; MacRoman; en_US (nb)

Observed: When working with multithread application i set line breakpoint to suspend all threads, after it was hit i resumed one of the threads and invoked 
Debug|Check for deadlock - see attached messages log (was unable to take threaddump because of the out of memory error) unfortunately could not 
reproduce it

Comment 1 Petr Cyhelsky 2008-08-19 17:58:08 UTC

Created attachment 67835 [details]
messages.log

Comment 2 Petr Cyhelsky 2008-08-19 18:13:28 UTC

when i tried to take threaddump using jstack it couldn't attach to the process and when i tried to get it using kill -3
it couldn't find the process - this seems similar to what happened to reporter of Issue #140823

Comment 3 Martin Entlicher 2008-08-20 10:52:15 UTC

Hmm, we can not do anything about it without the thread dump. :-(

Comment 4 Petr Cyhelsky 2008-08-20 11:28:53 UTC

And the java.io.IOException and java.lang.OutOfMemoryError at the end of messages.log file don't have anything in common
with the freeze ?

Comment 5 Martin Entlicher 2008-08-20 13:01:48 UTC

We do not know anything about the freeze, since we do not have the thread dump.
The exceptions in message.log do not seem to be related. But OutOfMemoryError usually means that the state of the
application is corrupted and it needs to be restarted. The application can not continue due to insufficient memory.
Since the OOME occurred in the EventDispatchThread, the application may look like not responding.

Comment 6 Martin Entlicher 2008-08-20 13:16:11 UTC

Next time when this happens, please make at least a heap dump. From that we could find out if there's a memory leak
somewhere. It might be in debugger, or in can be a coincident that the OOME happend just during debugging.

Comment 7 Petr Cyhelsky 2008-09-01 09:29:24 UTC

For now I'm unable to reproduce it - lowering priority.

Comment 8 Peter Pis 2008-12-02 13:00:36 UTC

Without requested information for long time - INVALID. We can't do anything in this case. Reporter, please add requested
information and reopen issue. Thanks in advance.

Comment 9 Quality Engineering 2010-04-29 09:43:04 UTC

Verified ... and Closing all issues resolved into NetBeans 6.7 and earlier.