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.

Bug 212205 - OutOfMemoryError: unable to create new native thread
Summary: OutOfMemoryError: unable to create new native thread
Status: RESOLVED INVALID
Alias: None
Product: platform
Classification: Unclassified
Component: -- Other -- (show other bugs)
Version: 7.2
Hardware: All All
: P3 normal (vote)
Assignee: Antonin Nebuzelsky
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-05-08 21:54 UTC by javydreamercsw
Modified: 2012-06-05 12:58 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter: 187762

Attachments
stacktrace (3.06 KB, text/plain)
2012-05-08 21:54 UTC, javydreamercsw 		Details
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description javydreamercsw 2012-05-08 21:54:23 UTC 
Build: NetBeans IDE Dev (Build 201205070400)
VM: Java HotSpot(TM) Client VM, 23.0-b21, Java(TM) SE Runtime Environment, 1.7.0_04-b20
OS: Windows 7

User Comments:
javydreamercsw: Running JUnit tests




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:691)
   at org.netbeans.Stamps$Worker.start(Stamps.java:797)
   at org.netbeans.Stamps.flush(Stamps.java:274)
   at org.netbeans.Stamps.waitFor(Stamps.java:311)
   at org.netbeans.Stamps.shutdown(Stamps.java:280)
Comment 1 javydreamercsw 2012-05-08 21:54:29 UTC 
Created attachment 119179 [details]
stacktrace
Comment 2 Antonin Nebuzelsky 2012-06-05 10:41:18 UTC 
Too many threads created? Or other system resources exhausted? Memory, or disk full?

Could you please provide more information about the condition of your system and of the NetBeans process?

A thread dump (jps, jstack on command line) of NetBeans might help. Thanks.
Comment 3 javydreamercsw 2012-06-05 12:58:42 UTC 
In all my cases it's been memory resource full. As you can see from the attachment the stacktrace doesn't work properly. The good thing is that I haven't seen this issue on recent builds, for some weeks now. So I'll mark it as invalid unless it happens again.