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 222267

Summary:	OutOfMemoryError: GC overhead limit exceeded
Product:	javascript	Reporter:	augcampos
Component:	Editor	Assignee:	Petr Hejl <phejl>
Status:	RESOLVED INCOMPLETE
Severity:	normal	CC:	ovrabec
Priority:	P3	Keywords:	PERFORMANCE
Version:	7.3
Hardware:	All
OS:	All
Issue Type:	DEFECT	Exception Reporter:	195266
Attachments:	stacktrace stacktrace

Description augcampos 2012-11-16 12:38:11 UTC

Build: NetBeans IDE Dev (Build 201211160001)
VM: Java HotSpot(TM) 64-Bit Server VM, 23.5-b02, Java(TM) SE Runtime Environment, 1.7.0_09-b05
OS: Linux

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:722)

Comment 1 augcampos 2012-11-16 12:38:14 UTC

Created attachment 127931 [details]
stacktrace

Comment 2 Tomas Hurka 2012-11-16 15:17:45 UTC

OOME is caused by parsing very large javascript file - it has 970,000 characters.

Comment 3 Ondrej Vrabec 2013-07-30 12:28:01 UTC

Created attachment 137997 [details]
stacktrace

while debugging NetBeans and got down into JDK sources

Comment 4 Petr Hejl 2013-07-31 08:31:16 UTC

The last report from Ondrej is not related to JS.
Tomasi can you share the file with us? Is it still happening?