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 238990 - Opening huge heap dump OOME: GC overhead limit exceeded
Summary: Opening huge heap dump OOME: GC overhead limit exceeded
Alias: None
Product: profiler
Classification: Unclassified
Component: Base (show other bugs)
Version: 7.4
Hardware: All All
: P3 normal (vote)
Assignee: issues@profiler
Depends on:
Reported: 2013-11-30 03:33 UTC by jbosboom
Modified: 2015-04-22 09:20 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter: 205678

stacktrace (1.14 KB, text/plain)
2013-11-30 03:33 UTC, jbosboom

Note You need to log in before you can comment on or make changes to this bug.
Description jbosboom 2013-11-30 03:33:05 UTC
Build: NetBeans IDE 7.4 (Build 201310111528)
VM: Java HotSpot(TM) 64-Bit Server VM, 24.45-b08, Java(TM) SE Runtime Environment, 1.7.0_45-b18
OS: Windows 7

User Comments:
jbosboom: I opened a large heap dump.  I'm not surprised it required a lot of memory, and while perhaps that code could scale better, I really ought to have the option to cancel once my computer starts paging.  (Even closing the heap dump's tab didn't stop parsing the heap dump.)

java.lang.OutOfMemoryError: GC overhead limit exceeded
   at java.lang.String.toCharArray(
   at java.util.jar.JarFile.getEntry(
   at org.netbeans.JarClassLoader$JarSource.resource(
   at org.netbeans.Archive.getData(
Comment 1 jbosboom 2013-11-30 03:33:07 UTC
Created attachment 142737 [details]
Comment 2 Jaroslav Tulach 2013-12-09 15:56:27 UTC
The user report talks about using profiler. Passing.
Comment 3 Tomas Hurka 2015-04-22 09:20:06 UTC
This should be fixed in latest dev. build. Opening heap dump should require a lot less memory.