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 233824 - OutOfMemoryError: GC overhead limit exceeded
Summary: OutOfMemoryError: GC overhead limit exceeded
Status: RESOLVED FIXED
Alias: None
Product: debugger
Classification: Unclassified
Component: Java (show other bugs)
Version: 7.4
Hardware: All All
: P3 normal (vote)
Assignee: Martin Entlicher
URL:
Keywords: PERFORMANCE
Depends on:
Blocks:
 
Reported: 2013-08-02 08:05 UTC by Ondrej Vrabec
Modified: 2013-08-28 16:39 UTC (History)
2 users (show)

See Also:
Issue Type: DEFECT
Exception Reporter: 202750

Attachments
stacktrace (475 bytes, text/plain)
2013-08-02 08:05 UTC, Ondrej Vrabec 		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 Ondrej Vrabec 2013-08-02 08:05:15 UTC 
This issue was reported manually by ovrabec.
It already has 1 duplicates 


Build: NetBeans IDE Dev (Build 20130729-3bf4ccccea72)
VM: Java HotSpot(TM) 64-Bit Server VM, 23.25-b01, Java(TM) SE Runtime Environment, 1.7.0_25-b15
OS: Linux

User Comments:
ovrabec: while debugging NetBeans and got down into JDK sources




Stacktrace: 
java.lang.OutOfMemoryError: GC overhead limit exceeded
   at java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.addConditionWaiter(AbstractQueuedSynchronizer.java:1857)
   at java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.awaitNanos(AbstractQueuedSynchronizer.java:2073)
   at java.util.concurrent.DelayQueue.take(DelayQueue.java:220)
   at javax.swing.TimerQueue.run(TimerQueue.java:171)
   at java.lang.Thread.run(Thread.java:724)
Comment 1 Ondrej Vrabec 2013-08-02 08:05:16 UTC 
Created attachment 138169 [details]
stacktrace
Comment 2 Petr Cyhelsky 2013-08-02 08:28:24 UTC 
there are 10 instances of symtab, please evaluate
Comment 3 Jan Lahoda 2013-08-02 08:55:22 UTC 
I guess this can be split into two distinct problems:
-the javac instances are too big - same as bug #231565 IMO (exact cause unknown)
-8 of the 10 instances of javac appear to be held by the debugger - feels like a little bit too much.
Comment 4 Martin Entlicher 2013-08-15 17:02:48 UTC 
It looks like parseWhenScanFinishedReallyLazy() is scheduled several times.
Comment 5 Martin Entlicher 2013-08-28 16:39:59 UTC 
Fixed by changeset:   262927:098cb060d71d
http://hg.netbeans.org/core-main/rev/098cb060d71d