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 150434 - ObjectCollectionException thrown - NOT recoverable
Summary: ObjectCollectionException thrown - NOT recoverable
Status: VERIFIED FIXED
Alias: None
Product: debugger
Classification: Unclassified
Component: Code (show other bugs)
Version: 6.x
Hardware: All Windows XP
: P1 blocker (vote)
Assignee: issues@debugger
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-10-16 20:04 UTC by ddmiller
Modified: 2008-11-24 09:42 UTC (History)
3 users (show)

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments
Requested thread dump of the problem (28.89 KB, text/plain)
2008-10-17 15:32 UTC, ddmiller
Details
Picture of the screen at time of error (444.49 KB, image/jpeg)
2008-10-17 15:33 UTC, ddmiller
Details

Note You need to log in before you can comment on or make changes to this bug.
Description ddmiller 2008-10-16 20:04:36 UTC
When I press a button on my UI, I get an ObjectCollectedException.  The dialog box pops up that sez the system should 
continue working but the dialog itself is non-responsive and none of the buttons work.  I cannot dismiss the dialog 
and I cannot continue debugging my app.  I have to go to TaskManager and kill NB and start over.
Comment 1 Marian Mirilovic 2008-10-17 07:36:34 UTC
Hi ddmiller,
thanks for your report, but unfortunately we are not able to reproduce your issue. Could you please provide more
informations (IDE build, JDK version, exception's stack-trace, ....) :
http://wiki.netbeans.org/IssueReportingGuidelines
Thanks in advance,
*Marian
Comment 2 Peter Pis 2008-10-17 08:39:58 UTC
Could you please attach thread dump?

http://wiki.netbeans.org/GenerateThreadDump
Comment 3 ddmiller 2008-10-17 15:19:07 UTC
I didn't know what attachments you needed.  Now I have VisualVM installed and am ready to get the stack trace.  
Unfortunately, now I can't recreate the problem either.  When I encountered it yesterday, the code I was working on 
was incomplete and the problem happened every time.  After reporting the issue, I continued work on that code and now 
it doesn't fail.

So, if I see it happen again, I will generate the proper documentation and submit it.
Comment 4 ddmiller 2008-10-17 15:32:29 UTC
Created attachment 72134 [details]
Requested thread dump of the problem
Comment 5 ddmiller 2008-10-17 15:33:44 UTC
Created attachment 72135 [details]
Picture of the screen at time of error
Comment 6 ddmiller 2008-10-17 15:39:27 UTC
I just recreated the problem following a different path.

Any other documentation you need?

From IDE About:

Product Version: NetBeans IDE Dev (Build 200807040101)
Java: 1.6.0_07; Java HotSpot(TM) Client VM 10.0-b23
System: Windows XP version 5.1 running on x86; Cp1252; en_US (nb)
Userdir: C:\Documents and Settings\dm185016\.netbeans\6.5m1

Note:  I am NOT using the beta as when I tried it was too unstable to use to get any work done.  I have been using the 
M1 milestone.  If a newer version of the beta that was more stable was available I would change.
Comment 7 Martin Entlicher 2008-10-17 16:49:33 UTC
It might be a similar problem to issue #150311.
Please also attach the messages.log file from <NetBeans user-dir>/var/log/messages.log There should be the complete
stack-trace of the ObjectCollectionException.

There does not seem to be anything blocked in the thread dump, but maybe AWT-EventQueue is busy in some loop.
Can you please try the same use-case with the latest 6.5 build from
http://bits.netbeans.org/dev/nightly/2008-10-17_02-01-18/  That should be nearly 6.5 RC quality and there was a lot of
fixes since beta.
Thank you.
Comment 8 Martin Entlicher 2008-10-17 16:55:11 UTC
Also, can you please check when this happens whether NetBeans consume a lot of CPU? If yes, it's really busy in some
loop and we'd love to have some sample application on which we could reproduce the problem.
Anyway it's important to know if the problem persists in the latest 6.5 dev build.
Comment 9 ddmiller 2008-10-17 18:34:51 UTC
Wow!  Thanks for the suggestion to switch to the nightly build.  Its MUCH faster!  After installing it I can no longer 
recreate the problem.  If it happens again, I will update this bug.
Comment 10 Martin Entlicher 2008-10-23 13:21:18 UTC
So I hope that this was fixed in latest 6.5 build.
If the problem reappears please reopen this and attach the messages.log file and some steps to reproduce.
Thank you.
Comment 11 matusdekanek 2008-11-24 09:42:57 UTC
issue is over a month old and does seem to be resolved
I think it can be marked as verified