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

Summary:	Opening huge heap dump OOME: GC overhead limit exceeded
Product:	profiler	Reporter:	jbosboom <jbosboom>
Component:	Base	Assignee:	issues@profiler <issues>
Status:	RESOLVED FIXED
Severity:	normal
Priority:	P3
Version:	7.4
Hardware:	All
OS:	All
Issue Type:	DEFECT	Exception Reporter:	205678
Attachments:	stacktrace

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.)




Stacktrace: 
java.lang.OutOfMemoryError: GC overhead limit exceeded
   at java.lang.String.toCharArray(String.java:2753)
   at java.util.zip.ZipCoder.getBytes(ZipCoder.java:78)
   at java.util.zip.ZipFile.getEntry(ZipFile.java:306)
   at java.util.jar.JarFile.getEntry(JarFile.java:226)
   at org.netbeans.JarClassLoader$JarSource.resource(JarClassLoader.java:595)
   at org.netbeans.Archive.getData(Archive.java:212)

Comment 1 jbosboom 2013-11-30 03:33:07 UTC

Created attachment 142737 [details]
stacktrace

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.