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 155744 - OutOfMemoryError after opening a yaml file
Summary: OutOfMemoryError after opening a yaml file
Status: RESOLVED FIXED
Alias: None
Product: web
Classification: Unclassified
Component: YAML (show other bugs)
Version: 6.x
Hardware: All All
: P1 blocker (vote)
Assignee: Torbjorn Norbye
URL:
Keywords:
: 156072 (view as bug list)
Depends on:
Blocks:
 
Reported: 2008-12-18 12:45 UTC by Petr Pisl
Modified: 2009-02-23 14:58 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:

Attachments
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 Petr Pisl 2008-12-18 12:45:48 UTC 
Just open a yaml file or create new one in a trunk build and you obtain: 

Caused by: java.lang.OutOfMemoryError: Java heap space
	at java.util.Arrays.copyOf(Arrays.java:2760)
	at java.util.Arrays.copyOf(Arrays.java:2734)
	at java.util.ArrayList.ensureCapacity(ArrayList.java:167)
	at java.util.ArrayList.add(ArrayList.java:351)
	at org.netbeans.modules.languages.yaml.YamlParser.parse(YamlParser.java:152)
	at org.netbeans.modules.languages.yaml.YamlParser.parseFiles(YamlParser.java:244)
	at org.netbeans.napi.gsfret.source.Source.moveToPhase(Source.java:1064)
	at org.netbeans.napi.gsfret.source.Source$CompilationJob.run(Source.java:1407)
	at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441)
	at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
	at java.util.concurrent.FutureTask.run(FutureTask.java:138)
	at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
	at java.lang.Thread.run(Thread.java:619)
Comment 1 Martin Krauskopf 2008-12-18 12:57:50 UTC 
I can't reproduce in 60 min old trunk. Could you try more recent build?
Comment 2 Petr Pisl 2008-12-18 13:41:43 UTC 
It was build from this morning. Now I have update and rebuild again and it's still reproducible. We are able to also
reproduce on Erno's machine. Just create an yaml file and wait a few seconds. The processor is consumed for 100%
percent, so it looks like there is a never ending cycle.
Comment 3 Erno Mononen 2009-01-08 09:35:01 UTC 
This seems to be fixed by Tor in b88974f215c6.
Comment 4 Erno Mononen 2009-02-23 14:58:33 UTC 
*** Issue 156072 has been marked as a duplicate of this issue. ***