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 167360 - [67cat] com.sun.jdi.VMOutOfMemoryException at com.sun.tools.jdi.JDWPException.toJDIException
Summary: [67cat] com.sun.jdi.VMOutOfMemoryException at com.sun.tools.jdi.JDWPException...
Status: CLOSED INCOMPLETE
Alias: None
Product: debugger
Classification: Unclassified
Component: Java (show other bugs)
Version: 6.x
Hardware: All All
: P3 blocker (vote)
Assignee: issues@debugger
URL: http://statistics.netbeans.org/except...
Keywords:
Depends on:
Blocks:
 
Reported: 2009-06-19 10:53 UTC by nleck
Modified: 2010-05-06 11:51 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter: 152808

Attachments
stacktrace (553 bytes, text/plain)
2009-06-19 10:53 UTC, nleck 		Details
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description nleck 2009-06-19 10:53:42 UTC 
Build: NetBeans IDE Dev (Build 200906180201)
VM: Java HotSpot(TM) 64-Bit Server VM, 11.3-b02, Java(TM) SE Runtime Environment, 1.6.0_13-b03
OS: Linux, 2.6.27.21-170.2.56.fc10.x86_64, amd64

Stacktrace: 
com.sun.jdi.VMOutOfMemoryException
        at com.sun.tools.jdi.JDWPException.toJDIException(JDWPException.java:31)
        at com.sun.tools.jdi.ThreadReferenceImpl.threadGroup(ThreadReferenceImpl.java:239)
        at org.netbeans.modules.debugger.jpda.jdi.ThreadReferenceWrapper.threadGroup(ThreadReferenceWrapper.java:581)
        at org.netbeans.modules.debugger.jpda.models.ThreadsCache.exec(ThreadsCache.java:312)
        at org.netbeans.modules.debugger.jpda.util.Operator$1.run(Operator.java:352)
        at java.lang.Thread.run(Thread.java:619)
Comment 1 nleck 2009-06-19 10:53:48 UTC 
Created attachment 83797 [details]
stacktrace
Comment 2 Daniel Prusa 2009-06-29 13:53:31 UTC 
VMOutOfMemoryException indicates that the debugged VM has run out of memory. Can you provide more information on the
situation when it occurred, please?
Were there sufficient memory resources for the debugged VM?
Is it reproducible?
Comment 3 Vojtech Sigler 2009-09-18 13:00:43 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 4 Marian Mirilovic 2010-05-06 11:51:34 UTC 
closing incomplete issues