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 249558 - OutOfMemoryError: Java heap space
Summary: OutOfMemoryError: Java heap space
Status: RESOLVED DUPLICATE of bug 243837
Alias: None
Product: debugger
Classification: Unclassified
Component: Java (show other bugs)
Version: 8.0
Hardware: All All
: P3 normal (vote)
Assignee: Martin Entlicher
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-12-29 13:42 UTC by whbogado
Modified: 2015-01-02 17:11 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter: 213270

Attachments
stacktrace (1.18 KB, text/plain)
2014-12-29 13:42 UTC, whbogado 		Details
UI LOG (3.31 KB, application/octet-stream)
2014-12-31 19:31 UTC, soundgod1818 		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 whbogado 2014-12-29 13:42:08 UTC 
Build: NetBeans IDE 8.0.2 (Build 201411181905)
VM: Java HotSpot(TM) 64-Bit Server VM, 25.20-b23, Java(TM) SE Runtime Environment, 1.8.0_20-b26
OS: Windows 8

User Comments:
whbogado: Working on a Web/JSF application with Tomcat 8.0.15.

GUEST: Left NB 8.0.1 running overnight




Stacktrace: 
java.lang.OutOfMemoryError: Java heap space
   at java.util.HashMap.resize(HashMap.java:703)
   at java.util.HashMap.putVal(HashMap.java:662)
   at java.util.HashMap.put(HashMap.java:611)
   at com.sun.tools.jdi.TargetVM.send(TargetVM.java:283)
   at com.sun.tools.jdi.VirtualMachineImpl.sendToTarget(VirtualMachineImpl.java:1032)
   at com.sun.tools.jdi.PacketStream.send(PacketStream.java:59)
Comment 1 whbogado 2014-12-29 13:42:09 UTC 
Created attachment 151309 [details]
stacktrace
Comment 2 soundgod1818 2014-12-31 19:31:06 UTC 
Created attachment 151333 [details]
UI LOG

OutOfMemoryError: Java heap space
Comment 3 soundgod1818 2014-12-31 19:31:41 UTC 
I am having the same problem
Comment 4 Martin Entlicher 2015-01-02 17:11:04 UTC 
This is a duplicate of issue #243837.
But it's nice, that in http://statistics.netbeans.org/exceptions/heaplog?id=759540 there happens to be a thread, that is just throwing ClosedConnectionException on a packet send:
om.sun.jdi.connect.spi.ClosedConnectionException.<init>(ClosedConnectionException.java:65) 	at com.sun.tools.jdi.SharedMemoryConnection.writePacket(SharedMemoryConnection.java:104) 	at com.sun.tools.jdi.TargetVM.send(TargetVM.java:291) 	at com.sun.tools.jdi.VirtualMachineImpl.sendToTarget(VirtualMachineImpl.java:1032) 	at com.sun.tools.jdi.PacketStream.send(PacketStream.java:59) 	at com.sun.tools.jdi.JDWP$ThreadReference$Status.enqueueCommand(JDWP.java:5086)

The JDI backend still caches the sent packets despite the fact that VM was disconnected already.

*** This bug has been marked as a duplicate of bug 243837 ***