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 209270

Summary: OutOfMemoryError: Java heap space
Product: editor Reporter: merlyn333
Component: Parsing & IndexingAssignee: Tomas Zezula <tzezula>
Status: RESOLVED DUPLICATE    
Severity: normal    
Priority: P3    
Version: 7.1   
Hardware: All   
OS: All   
Issue Type: DEFECT Exception Reporter: 181821
Attachments: stacktrace

Description merlyn333 2012-03-07 13:59:49 UTC
Build: NetBeans IDE 7.1 (Build 201112071828)
VM: OpenJDK 64-Bit Server VM, 20.0-b11, OpenJDK Runtime Environment, 1.6.0_23-b23
OS: Linux

User Comments:
merlyn333: I updated Netbeans IDE and when I execute NetBeans app, the system starts to browse my projects to identify changes, but it get stuck at 33%.

GUEST: Scanning is always a problem - scanning is running for hours although only four projects are opened. The projects reside on various vpn networks that are not always available. Perhaps that' a problem. Installing Scanning on Demand did not solve the problem. The Tasks window is closed.

GUEST: startup of IDE, scanning projects is running and gets to the html folder of my project, memory builds up, a message flashes that its enabling the HTML validator, memory builds up to heap limit and then the error occurs, appears scanning stops after the error.




Stacktrace: 
java.lang.OutOfMemoryError: Java heap space
   at java.util.Arrays.copyOf(Arrays.java:2894)
   at java.lang.AbstractStringBuilder.expandCapacity(AbstractStringBuilder.java:117)
   at java.lang.AbstractStringBuilder.append(AbstractStringBuilder.java:407)
   at java.lang.StringBuilder.append(StringBuilder.java:136)
   at java.lang.StringBuilder.append(StringBuilder.java:184)
   at org.netbeans.modules.parsing.api.Embedding.create(Embedding.java:108)
Comment 1 merlyn333 2012-03-07 13:59:52 UTC
Created attachment 116429 [details]
stacktrace
Comment 2 Tomas Zezula 2012-06-11 18:26:19 UTC
Seems as a duplicate of issue # 207991

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