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.
This bug was originally marked as duplicate of bug 195722, that is already resolved. This bug is still valid, so this seems to be another bug, but it might be related. Build: NetBeans IDE 8.0 (Build 201403101706) VM: Java HotSpot(TM) Client VM, 24.45-b08, Java(TM) SE Runtime Environment, 1.7.0_45-b18 OS: Windows 8 User Comments: markhorner: I had NB8.0 minimized while watching a TV program on Mozilla Firefox v 27.0.1 and then got an out of memory message to close down NB.. Stacktrace: java.lang.OutOfMemoryError: unable to create new native thread at java.lang.Thread.start0(Thread.java:0) at java.lang.Thread.start(Thread.java:713) at org.openide.util.RequestProcessor$Processor.get(RequestProcessor.java:1906) at org.openide.util.RequestProcessor.enqueue(RequestProcessor.java:610) at org.openide.util.RequestProcessor$Task.schedule(RequestProcessor.java:1493) at org.openide.util.RequestProcessor$Task.schedule(RequestProcessor.java:1464)
Created attachment 146249 [details] stacktrace
Since I reported the issue to you I have updated to Firefox 28.0 from Firefox 27.0.1. However, significantly (i) I do not get the NB 8.0 out-of-memory message when I am not running Firefox 28.0. NB 8.0 runs like a charm, and (ii) I get the out-of-memory issue in Firefox when I am running Firefox on its own. And that suggests that the cause of the memory leak lies with Firefox and that NB is not the cause but the victim.
O.K. so it looks like a system problem - there's a lack of native threads. Since you describe a connection to Firefox, it might be that the older version consumed a lot of system threads and then NetBeans could not allocate new threads. NetBeans uses RequestProcessor to limit the number of threads (that can be seen from the exception stack trace), therefore the real cause of the issue seems to lie elsewhere. Thanks for your observation.