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 267464 - OutOfMemoryError: GC overhead limit exceeded
Summary: OutOfMemoryError: GC overhead limit exceeded
Status: RESOLVED WONTFIX
Alias: None
Product: javascript
Classification: Unclassified
Component: Editor (show other bugs)
Version: 8.1
Hardware: All All
: P3 normal (vote)
Assignee: Petr Pisl
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-08-07 01:58 UTC by pborregg
Modified: 2016-08-17 12:50 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter: 225654


Attachments
stacktrace (2.73 KB, text/plain)
2016-08-07 01:58 UTC, pborregg
Details

Note You need to log in before you can comment on or make changes to this bug.
Description pborregg 2016-08-07 01:58:49 UTC
Build: NetBeans IDE 8.1 (Build 201510222201)
VM: Java HotSpot(TM) 64-Bit Server VM, 25.91-b14, Java(TM) SE Runtime Environment, 1.8.0_91-b14
OS: Windows 10

User Comments:
pborregg: Dunno, I was launching it again and got this weird ass error... Restarted my computer and all is well.




Stacktrace: 
java.lang.OutOfMemoryError: GC overhead limit exceeded
   at org.mozilla.javascript.NativeCall.<init>(NativeCall.java:55)
   at org.mozilla.javascript.ScriptRuntime.createFunctionActivation(ScriptRuntime.java:3184)
   at org.mozilla.javascript.gen.jshint_2_9_2_js_1._c_anonymous_612(jshint_2_9_2_js_1.java:0)
   at org.mozilla.javascript.gen.jshint_2_9_2_js_1.call(jshint_2_9_2_js_1.java:0)
   at org.mozilla.javascript.optimizer.OptRuntime.callProp0(OptRuntime.java:85)
   at org.mozilla.javascript.gen.jshint_2_9_2_js_1._c_anonymous_616(jshint_2_9_2_js_1.java:15137)
Comment 1 pborregg 2016-08-07 01:58:51 UTC
Created attachment 161581 [details]
stacktrace
Comment 2 Tomas Hurka 2016-08-08 07:59:56 UTC
There are a lot of javascript files and javascript related objects. All seems to be connected to static HashMap annotations in JSHintErrorAnnotation.
Comment 3 Petr Pisl 2016-08-08 11:54:58 UTC
This is already fixed in patch 1.
Comment 4 Petr Pisl 2016-08-08 20:12:53 UTC
Probably the fix in the patch doesn't fix this case. But then it looks like there is used a third party plugin. So it can be connected with this one.
Comment 5 Petr Pisl 2016-08-17 12:50:39 UTC
The problems comes from a third party plugin. I can see at least many classes from org.mozilla.javascript.optimizer and org.mozilla.javascript.gen etc.

You can file a bug against the third party plugin.