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 218586 - OutOfMemoryError: Java heap space
Summary: OutOfMemoryError: Java heap space
Status: RESOLVED INCOMPLETE
Alias: None
Product: editor
Classification: Unclassified
Component: Lexer (show other bugs)
Version: 7.1
Hardware: All All
: P3 normal (vote)
Assignee: Miloslav Metelka
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-09-19 03:59 UTC by Exceptions Reporter
Modified: 2012-11-09 08:50 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter: 166476

Attachments
stacktrace (3.04 KB, text/plain)
2012-09-19 03:59 UTC, Exceptions Reporter 		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 Exceptions Reporter 2012-09-19 03:59:42 UTC 
This bug was originally marked as duplicate of bug 183289, that is already resolved. This bug is still valid, so this seems to be another bug, but it might be related.

Build: NetBeans IDE 7.1.2 (Build 201204101705)
VM: Java HotSpot(TM) Client VM, 23.1-b03, Java(TM) SE Runtime Environment, 1.7.0_05-b06
OS: Windows 7

User Comments:
GUEST: I just started netbeans it scanned the (php) proj4ects and then .. i got this message

GUEST: open zend project

GUEST: Now i closed the tast window, but when I start netbeans I get this error.

I will now close one project




Stacktrace: 
java.lang.OutOfMemoryError: Java heap space
   at java.util.Arrays.copyOf(Arrays.java:2245)
   at java.util.Arrays.copyOf(Arrays.java:2219)
   at java.util.ArrayList.trimToSize(ArrayList.java:167)
   at org.netbeans.lib.lexer.BatchTokenList.tokenOrEmbeddingImpl(BatchTokenList.java:190)
   at org.netbeans.lib.lexer.BatchTokenList.tokenOrEmbedding(BatchTokenList.java:173)
   at org.netbeans.api.lexer.TokenSequence.moveNext(TokenSequence.java:457)
Comment 1 Exceptions Reporter 2012-09-19 03:59:45 UTC 
Created attachment 124549 [details]
stacktrace
Comment 2 David Strupl 2012-11-09 08:50:39 UTC 
Without a heap dump out of memory problems cannot be fixed. In the newer versions the heap dump is sent automatically. Closing this report as incomplete.