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 253256 - OutOfMemoryError: GC overhead limit exceeded
Summary: OutOfMemoryError: GC overhead limit exceeded
Status: RESOLVED DUPLICATE of bug 253201
Alias: None
Product: java
Classification: Unclassified
Component: Navigation (show other bugs)
Version: 8.1
Hardware: All All
: P3 normal (vote)
Assignee: Tomas Zezula
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-06-30 09:22 UTC by Exceptions Reporter
Modified: 2015-06-30 09:23 UTC (History)
1 user (show)

See Also:
Issue Type: DEFECT
Exception Reporter: 218238


Attachments
stacktrace (2.84 KB, text/plain)
2015-06-30 09:22 UTC, Exceptions Reporter
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Exceptions Reporter 2015-06-30 09:22:18 UTC
This issue was reported manually by thurka.
It already has 1 duplicates 


Build: NetBeans IDE Dev (Build 201506250001)
VM: Java HotSpot(TM) 64-Bit Server VM, 25.31-b07, Java(TM) SE Runtime Environment, 1.8.0_31-b13
OS: Mac OS X

User Comments:
GUEST: The memory usage randomly starts growing and doesn't stop while it is scanning the projects. It reaches about 960MB before it starts having issues - uses all 8 CPUs and starts reporting memory errors.




Stacktrace: 
java.lang.OutOfMemoryError: GC overhead limit exceeded
   at java.lang.AbstractStringBuilder.<init>(AbstractStringBuilder.java:68)
   at java.lang.StringBuffer.<init>(StringBuffer.java:116)
   at java.io.StringWriter.<init>(StringWriter.java:50)
   at com.sun.tools.javac.tree.JCTree.toString(JCTree.java:410)
   at org.netbeans.modules.java.navigation.BreadCrumbsNodeImpl.createBreadcrumbs(BreadCrumbsNodeImpl.java:284)
   at org.netbeans.modules.java.navigation.BreadCrumbsNodeImpl$3$1.scan(BreadCrumbsNodeImpl.java:465)
Comment 1 Exceptions Reporter 2015-06-30 09:22:20 UTC
Created attachment 154437 [details]
stacktrace
Comment 2 Tomas Hurka 2015-06-30 09:23:48 UTC

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