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 254467 - 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: 2015-08-18 07:10 UTC by dhuyvetter
Modified: 2015-08-24 12:53 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter: 219253

Attachments
stacktrace (2.69 KB, text/plain)
2015-08-18 07:10 UTC, dhuyvetter 		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 dhuyvetter 2015-08-18 07:10:21 UTC 
This bug was originally marked as duplicate of bug 221861, 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.2 (Build 201411181905)
VM: Java HotSpot(TM) 64-Bit Server VM, 25.51-b03, Java(TM) SE Runtime Environment, 1.8.0_51-b16
OS: Linux

User Comments:
dhuyvetter: I think my harddrive was close to full and that might have caused this error.

GUEST: not sure




Stacktrace: 
java.lang.OutOfMemoryError: GC overhead limit exceeded
   at org.antlr.runtime.Lexer.emit(Lexer.java:160)
   at org.netbeans.modules.css.lib.ExtCss3Lexer.nextToken(ExtCss3Lexer.java:127)
   at org.antlr.runtime.BufferedTokenStream.fetch(BufferedTokenStream.java:133)
   at org.antlr.runtime.BufferedTokenStream.sync(BufferedTokenStream.java:127)
   at org.antlr.runtime.CommonTokenStream.consume(CommonTokenStream.java:67)
   at org.antlr.runtime.debug.DebugTokenStream.consume(DebugTokenStream.java:60)
Comment 1 dhuyvetter 2015-08-18 07:10:24 UTC 
Created attachment 155416 [details]
stacktrace
Comment 2 Jan Stola 2015-08-24 12:53:22 UTC 

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