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 204890 - [71cat] OutOfMemoryError: unable to create new native thread
Summary: [71cat] OutOfMemoryError: unable to create new native thread
Status: RESOLVED DUPLICATE of bug 204359
Alias: None
Product: platform
Classification: Unclassified
Component: Favorites (show other bugs)
Version: 7.1
Hardware: All All
: P3 normal (vote)
Assignee: Ondrej Vrabec
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-11-09 13:51 UTC by muellermi
Modified: 2011-11-11 11:03 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter: 182737

Attachments
stacktrace (2.10 KB, text/plain)
2011-11-09 13:51 UTC, muellermi 		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 muellermi 2011-11-09 13:51:22 UTC 
Build: NetBeans IDE Dev (Build 201111080600)
VM: Java HotSpot(TM) Client VM, 21.1-b02, Java(TM) SE Runtime Environment, 1.7.0_01-b08
OS: Windows XP

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 javax.swing.plaf.basic.BasicDirectoryModel.validateFileCache(BasicDirectoryModel.java:141)
   at javax.swing.plaf.basic.BasicDirectoryModel.propertyChange(BasicDirectoryModel.java:69)
   at java.beans.PropertyChangeSupport.fire(PropertyChangeSupport.java:335)
   at java.beans.PropertyChangeSupport.firePropertyChange(PropertyChangeSupport.java:327)
Comment 1 muellermi 2011-11-09 13:51:25 UTC 
Created attachment 113046 [details]
stacktrace
Comment 2 Ondrej Vrabec 2011-11-09 14:04:23 UTC 
There should be a heap dump generated to C:\Dokumente und Einstellungen\muellermi\.netbeans\dev\var\log\heapdump.hprof, upload it so we can analyze it.
Comment 3 Tomas Stupka 2011-11-11 11:03:18 UTC 
i believe this is a duplicate

*** This bug has been marked as a duplicate of bug 204359 ***