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.
JVM flag -XX:+HeapDumpOnOutOfMemoryError does not create heap dump in case of "OutOfMemoryError: unable to create new native thread". It makes sense since this error is not really out of memory error, but exhaustion of native thread resource. However there is several hundreds of this reports in exception reporter and messages.log with last exception does not provide sufficient information to find out who creates several thousands of native threads. To get more information, uihandler module can heap dump itself if it finds out that there was OOME and there is no heap dump file. This way OOME will be reported with the heap dump. As a proof of concept see this exception report: http://statistics.netbeans.org/exceptions/exception.do?id=776809
Created attachment 153478 [details] Proposed patch
Done in profiler-main changeset: 286932:8563c3c60a24 user: Tomas Hurka <thurka@netbeans.org> date: Wed May 06 16:23:29 2015 +0200 summary: issue #252183, try to create heap dump if none was created by OOME
Integrated into 'main-silver', will be available in build *201505070001* on http://bits.netbeans.org/dev/nightly/ (upload may still be in progress) Changeset: http://hg.netbeans.org/main-silver/rev/8563c3c60a24 User: Tomas Hurka <thurka@netbeans.org> Log: issue #252183, try to create heap dump if none was created by OOME