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 251135 - OutOfMemoryError: Java heap space
Summary: OutOfMemoryError: Java heap space
Status: NEW
Alias: None
Product: serverplugins
Classification: Unclassified
Component: Tomcat (show other bugs)
Version: 8.0
Hardware: All All
: P3 normal (vote)
Assignee: Petr Hejl
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-03-12 17:44 UTC by Exceptions Reporter
Modified: 2015-03-16 11:11 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter: 216074

Attachments
stacktrace (2.41 KB, text/plain)
2015-03-12 17:44 UTC, Exceptions Reporter 		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 Exceptions Reporter 2015-03-12 17:44:40 UTC 
This bug was originally marked as duplicate of bug 183289, that is already resolved. This bug is still valid, so this seems to be another bug, but it might be related.

Build: NetBeans IDE 8.0.2 (Build 201411181905)
VM: Java HotSpot(TM) Client VM, 25.25-b02, Java(TM) SE Runtime Environment, 1.8.0_25-b18
OS: Windows 7

User Comments:
GUEST: System has 4 G physical memory of whihc 3 is usable. No other app is running and I get this error




Stacktrace: 
java.lang.OutOfMemoryError: Java heap space
   at sun.reflect.ByteVectorImpl.resize(ByteVectorImpl.java:84)
   at sun.reflect.ByteVectorImpl.add(ByteVectorImpl.java:63)
   at sun.reflect.ClassFileAssembler.emitByte(ClassFileAssembler.java:74)
   at sun.reflect.ClassFileAssembler.emitConstantPoolUTF8(ClassFileAssembler.java:104)
   at sun.reflect.AccessorGenerator.emitCommonConstantPoolEntries(AccessorGenerator.java:147)
   at sun.reflect.MethodAccessorGenerator.generate(MethodAccessorGenerator.java:349)
Comment 1 Exceptions Reporter 2015-03-12 17:44:41 UTC 
Created attachment 152582 [details]
stacktrace
Comment 2 Petr Hejl 2015-03-16 11:11:34 UTC 
Was there a huge amount of output in the output window when this happened?