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 215212 - com.sun.jdi.VMOutOfMemoryException at com.sun.tools.jdi.JDWPException.toJDIException
Summary: com.sun.jdi.VMOutOfMemoryException at com.sun.tools.jdi.JDWPException.toJDIEx...
Status: RESOLVED INCOMPLETE
Alias: None
Product: debugger
Classification: Unclassified
Component: Java (show other bugs)
Version: 7.2
Hardware: All All
: P3 normal (vote)
Assignee: Martin Entlicher
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-07-05 17:50 UTC by jomello_br
Modified: 2012-07-27 09:33 UTC (History)
4 users (show)

See Also:
Issue Type: DEFECT
Exception Reporter: 172861

Attachments
stacktrace (779 bytes, text/plain)
2012-07-05 17:50 UTC, jomello_br 		Details
stacktrace (779 bytes, text/plain)
2012-07-10 16:26 UTC, jomello_br 		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 jomello_br 2012-07-05 17:50:35 UTC 
Build: NetBeans IDE 7.2 Beta (Build 201205031832)
VM: Java HotSpot(TM) 64-Bit Server VM, 23.0-b21, Java(TM) SE Runtime Environment, 1.7.0_04-b22
OS: Windows 7

User Comments:
rptmaestro: Happened while debugging a web application.




Stacktrace: 
com.sun.jdi.VMOutOfMemoryException
   at com.sun.tools.jdi.JDWPException.toJDIException(JDWPException.java:49)
   at com.sun.tools.jdi.VirtualMachineImpl.redefineClasses(VirtualMachineImpl.java:354)
   at org.netbeans.modules.debugger.jpda.jdi.VirtualMachineWrapper.redefineClasses(VirtualMachineWrapper.java:2749)
   at org.netbeans.modules.debugger.jpda.JPDADebuggerImpl.fixClasses(JPDADebuggerImpl.java:471)
   at org.netbeans.modules.maven.debug.DebuggerChecker.reload(DebuggerChecker.java:245)
   at org.netbeans.modules.maven.debug.DebuggerChecker.executionResult(DebuggerChecker.java:174)
Comment 1 jomello_br 2012-07-05 17:50:39 UTC 
Created attachment 121769 [details]
stacktrace
Comment 2 Martin Entlicher 2012-07-10 14:30:20 UTC 
We need some concrete steps to reproduce.
The target virtual machine run out of memory, but it's not apparent why.
It can be also helpful if you can run the application that you are debugging with -XX:+HeapDumpOnOutOfMemoryError and provide the heap dump after the VMOutOfMemoryException is thrown.
Comment 3 jomello_br 2012-07-10 16:26:05 UTC 
Created attachment 121900 [details]
stacktrace