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.
Tried to create big java project (OpenJDK) as project with existing sources and NB was completely frozen after some time (during scanning). No OOMEs. Product Version: NetBeans IDE Dev (Build 200909030951) Java: 1.6.0_13; Java HotSpot(TM) Client VM 11.3-b02 System: Windows XP version 5.1 running on x86; Cp1252; en_US (nb)
Created attachment 87128 [details] thread dump
I'm sorry, but the dump shows nothing. No activity, no deadlock, it doesn't even contain the 'Parsing & Indexing Loop' thread. If this is reproducible please try again and use Profile Me! and attach the profiler snapshot here. It may also be useful to run the IDE with -J-Dorg.netbeans.modules.parsing.impl.indexing.RepositoryUpdater.level=FINE and attach it here. Thanks
I just attached a stack dump to bug#165137 where the IDE just locked up and needed to be killed.
I have 2Gb of RAM on my machine and if I run nb with default memory settings I get OOMEs during scanning of this project. And IDE is still somehow responsible (although slow). If I set -J-Xmx1024m - it completely hangs after some time and no 'exception' signs in IDE. But in messages.log there are a lot of exceptions.
Created attachment 87223 [details] attaching messages.log with exceptions
The exact steps to reproduce with a fresh checkout of OpenJDK and fresh install of NetBeans would be nice.
Let's wait for Dusan to analyze this. IIRC we used to be able to index openJDK project with -Xmx256m. From your log I can see that the IDE used -Xmx409m, which IMO should be enough.
The OOME is throw also when opening OpenJDK as freefrom project
I was able to open OpenJDK project (jdk/make/netbeans/j2se) with -J-Xmx192m after this patch: http://hg.netbeans.org/main-silver?cmd=changeset;node=3001175f7fd0
Fixed in the current dev build. http://hg.netbeans.org/main-silver?cmd=changeset;node=3001175f7fd0