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.
One more issue when NetBeans breaks in real production environment. When i build my web project which has thousands of classes and jsps. following error occurs. The system is out of resources. Consult the following stack trace for details. java.lang.OutOfMemoryError C:\Development\8.0Server\nbproject\build-impl.xml:364: The following error occurred while executing this line: C:\Development\8.0Server\nbproject\build-impl.xml:190: Compile failed; see the compiler error output for details. BUILD FAILED (total time: 37 seconds) The first link points to following line in Build-impl <webproject2:javac destdir="${build.classes.dir}"/> and second link points to <javac debug="@{debug}" deprecation="${javac.deprecation}" destdir="@{destdir}" encoding="${source.encoding}" executable="${platform.javac}" fork="yes" includeantruntime="false" source="${javac.source}" srcdir="@{srcdir}" target="${javac.target}" tempdir="${java.io.tmpdir}"> Log file at C:\Documents and Settings\sapan\.netbeans\6.0\var\log is not updated when this happens so no point in sending that..
http://wiki.netbeans.org/FaqOutofMemoryOnCompile
Well do you really think that it's true? This issue doesn't show up when I use Eclipse for same project. I think that increasing the memory is a work around and not a solution. When this issue happens on my NetBeans IDE I manually compile the packages/files till they are not in manageable number, can't this be done automatically?
Javac requires a certain amount of memory for compiling a source root of a certain size. If your source root is big, you can ask for more memory, and then it will work. There is no need to manually compile some subset of your files.