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 253967 - 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-07-30 06:54 UTC by ravi2katre
Modified: 2015-07-30 14:25 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter: 187507

Attachments
stacktrace (2.85 KB, text/plain)
2015-07-30 06:54 UTC, ravi2katre 		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 ravi2katre 2015-07-30 06:54:13 UTC 
Build: NetBeans IDE 8.0.2 (Build 201411181905)
VM: Java HotSpot(TM) 64-Bit Server VM, 25.11-b03, Java(TM) SE Runtime Environment, 1.8.0_11-b12
OS: Windows 8

User Comments:
ravi2katre: please check

GUEST: Writen HTML and CSS code, CPU consume excesive nearly 100%

GUEST: netbeans hungout while scan  for projects, only reaches 50
% and that's  it, application hangs..




Stacktrace: 
java.lang.OutOfMemoryError: GC overhead limit exceeded
   at org.netbeans.modules.css.lib.NbParseTreeBuilder.enterRule(NbParseTreeBuilder.java:127)
   at org.netbeans.modules.css.lib.Css3Parser.cssClass(Css3Parser.java:10097)
   at org.netbeans.modules.css.lib.Css3Parser.elementSubsequent(Css3Parser.java:9887)
   at org.netbeans.modules.css.lib.Css3Parser.simpleSelectorSequence(Css3Parser.java:9406)
   at org.netbeans.modules.css.lib.Css3Parser.selector(Css3Parser.java:9210)
   at org.netbeans.modules.css.lib.Css3Parser.selectorsGroup(Css3Parser.java:8911)
Comment 1 ravi2katre 2015-07-30 06:54:15 UTC 
Created attachment 155030 [details]
stacktrace
Comment 2 Jan Stola 2015-07-30 14:25:44 UTC 

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