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: NetBeans IDE Dev (Build 200910080418) VM: Java HotSpot(TM) Client VM, 14.2-b01, Java(TM) SE Runtime Environment, 1.6.0_16-b01 OS: SunOS, 5.11, x86 User Comments: vsigler: Invoked debug on a web project. Glassfish (v3) started and says deploying is done. If "Not enough space" refers to disk space, there's still more than 10G left. As for RAM, this machine (in virtualbox) has 1G. Stacktrace: java.io.IOException: error=12, Not enough space at java.lang.UNIXProcess.forkAndExec(UNIXProcess.java:0) at java.lang.UNIXProcess.<init>(UNIXProcess.java:53) at java.lang.ProcessImpl.start(ProcessImpl.java:65) at java.lang.ProcessBuilder.start(ProcessBuilder.java:452) at org.netbeans.modules.extbrowser.NbDefaultUnixBrowserImpl.setURL(NbDefaultUnixBrowserImpl.java:99) at org.openide.awt.HtmlBrowser$1URLSetter.run(HtmlBrowser.java:473)
Created attachment 89190 [details] stacktrace
This issue already has 9 duplicates see http://statistics.netbeans.org/exceptions/detail.do?id=152250
I also got this error when trying to open the newly added report from exceptions reporter. When I stopped debugging and stopped Glassfish, the problem vanished. Could it be caused by lack of free memory? If that's the case, NB should handle the exception a nicer way.
Ok, one more thing. Now this fired I am unable to debug a j2se project. Attaching output.
Created attachment 89199 [details] Output when trying to debug a j2se project after this problem occurred. Glassfish was already stopped at this moment.
No idea what the problem is. I assume there are no steps to reproduce reliably, marking as RANDOM.
I think this is really related to low virtual memory. I guess only message could be improved.
Last time this exception appeared was during 7.0 development cycle 2.5 years ago, so this was probably fixed by some other fix.