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 247206 - OutOfMemoryError: GC overhead limit exceeded
Summary: OutOfMemoryError: GC overhead limit exceeded
Status: RESOLVED DUPLICATE of bug 253306
Alias: None
Product: web
Classification: Unclassified
Component: CSS Visual Tools (show other bugs)
Version: 8.0
Hardware: All All
: P3 normal (vote)
Assignee: Jan Stola
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-09-17 10:57 UTC by Exceptions Reporter
Modified: 2015-07-07 15:51 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter: 211945


Attachments
stacktrace (2.71 KB, text/plain)
2014-09-17 10:57 UTC, Exceptions Reporter
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Exceptions Reporter 2014-09-17 10:57:27 UTC
This bug was originally marked as duplicate of bug 244697, that is already resolved. This bug is still valid, so this seems to be another bug, but it might be related.

Build: NetBeans IDE 8.0.1 (Build 201408251540)
VM: Java HotSpot(TM) 64-Bit Server VM, 25.5-b02, Java(TM) SE Runtime Environment, 1.8.0_05-b13
OS: Linux

User Comments:
GUEST: Connected my WIn8.1 Phone and boom :)




Stacktrace: 
java.lang.OutOfMemoryError: GC overhead limit exceeded
   at org.netbeans.modules.css.lib.CommonTokenUtil.getCommonTokenOffsetRange(CommonTokenUtil.java:68)
   at org.netbeans.modules.css.lib.TokenNode.<init>(TokenNode.java:59)
   at org.netbeans.modules.css.lib.NbParseTreeBuilder.consumeToken(NbParseTreeBuilder.java:228)
   at org.antlr.runtime.debug.DebugTokenStream.consume(DebugTokenStream.java:62)
   at org.antlr.runtime.BaseRecognizer.match(BaseRecognizer.java:106)
   at org.netbeans.modules.css.lib.Css3Parser.functionName(Css3Parser.java:12667)
Comment 1 Exceptions Reporter 2014-09-17 10:57:28 UTC
Created attachment 149292 [details]
stacktrace
Comment 2 Jan Stola 2015-07-07 15:51:42 UTC

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