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.
[ BUILD # : 200408191357 ] [ JDK VERSION : J2SE 1.5.0 ] That's the result of build project. The system is out of resources. Consult the following stack trace for details. java.lang.OutOfMemoryError <<no stack trace available>> BUILD FAILED (total time: 31 seconds)
meliandra, please provide more informations ! What was your workflow before OOME, is it 100 % reproducible, try to run Garbage Collector and try the same action again - is it reproducible, you HW description (RAM, ....) ? Thanks for report
I started the ide. Then I selected build project. My project consist of ~1600 classes. CPU 2,4 GHz, 1 GB RAM I haven't change any ide memory settings. I can "build" the whole project if I change the target directory. Yesterday I've installed the new q-build and forgot to change the target directory. So Netbeans compiled everything. Today I noticed this and changed it. Now I get compilation errors. So it seems that there's a problem if you compile a huge number of classes. For your information - There a call regarding performance during starting Netbeans. It takes over ten minutes on my machine. - I have also a lot of jars and compiled classes (24,000) without sources in my classpath.
OK, for very large individual compilations - i.e. when you have a large number of sources in a single package root, and perhaps also when the classpath is very large - javac simply requires more memory, because it needs to work with all those files at once. You will need to increase the -Xmx setting, e.g. in your netbeans.conf file. I think the default is currently 120Mb; with a gig of RAM you can afford to increase that. Or of course you could split up your sources into smaller modules, but this may or may not be an option depending on how you work and the rest of your team. I have no idea why starting the IDE would take ten minutes under any circumstances, but that is probably something unrelated. Might have to do with having a huge number (not size) of JARs in the classpath, or having large dirs of compiled classes not in JARs.