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 239318 - OutOfMemoryError: GC overhead limit exceeded
Summary: OutOfMemoryError: GC overhead limit exceeded
Status: RESOLVED DUPLICATE of bug 236118
Alias: None
Product: profiler
Classification: Unclassified
Component: Engine (show other bugs)
Version: 7.4
Hardware: All All
: P3 normal (vote)
Assignee: Tomas Hurka
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-12-10 14:18 UTC by aquaglia
Modified: 2013-12-10 15:01 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter: 205911


Attachments
stacktrace (3.33 KB, text/plain)
2013-12-10 14:19 UTC, aquaglia
Details

Note You need to log in before you can comment on or make changes to this bug.
Description aquaglia 2013-12-10 14:18:58 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:
aquaglia: Started profiler requesting stack allocation traces.

There is a bug already opened (since quite long)

Bug 236118 - OutOfMemoryError: Java heap space (edit)




Stacktrace: 
java.lang.OutOfMemoryError: GC overhead limit exceeded
   at org.netbeans.lib.profiler.results.memory.RuntimeMemoryCCTNode.clone(RuntimeMemoryCCTNode.java:149)
   at org.netbeans.lib.profiler.results.memory.RuntimeMemoryCCTNode.clone(RuntimeMemoryCCTNode.java:153)
   at org.netbeans.lib.profiler.results.memory.RuntimeMemoryCCTNode.clone(RuntimeMemoryCCTNode.java:153)
   at org.netbeans.lib.profiler.results.memory.RuntimeMemoryCCTNode.clone(RuntimeMemoryCCTNode.java:153)
   at org.netbeans.lib.profiler.results.memory.RuntimeMemoryCCTNode.clone(RuntimeMemoryCCTNode.java:153)
   at org.netbeans.lib.profiler.results.memory.RuntimeMemoryCCTNode.clone(RuntimeMemoryCCTNode.java:153)
Comment 1 aquaglia 2013-12-10 14:19:00 UTC
Created attachment 143013 [details]
stacktrace
Comment 3 Tomas Hurka 2013-12-10 15:01:27 UTC

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