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.
Summary: | java.io.IOException: error=12, Not enough space | ||
---|---|---|---|
Product: | ide | Reporter: | Vojtech Sigler <vsigler> |
Component: | Extbrowser | Assignee: | issues@ide <issues> |
Status: | RESOLVED FIXED | ||
Severity: | blocker | CC: | listolou, pjiricka, splineshaft |
Priority: | P3 | Keywords: | RANDOM |
Version: | 6.x | ||
Hardware: | All | ||
OS: | All | ||
URL: | http://statistics.netbeans.org/exceptions/detail.do?id=152250 | ||
Issue Type: | DEFECT | Exception Reporter: | 152250 |
Attachments: |
stacktrace
Output when trying to debug a j2se project after this problem occurred. Glassfish was already stopped at this moment. |
Description
Vojtech Sigler
2009-10-09 14:19:57 UTC
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. |