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 250341 - OutOfMemoryError: unable to create new native thread
Summary: OutOfMemoryError: unable to create new native thread
Status: RESOLVED WONTFIX
Alias: None
Product: javaee
Classification: Unclassified
Component: JSP Parser (show other bugs)
Version: 8.0
Hardware: All All
: P3 normal (vote)
Assignee: issues@javaee
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-02-10 12:42 UTC by pbradley
Modified: 2015-06-25 13:23 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter: 205487

Attachments
stacktrace (733 bytes, text/plain)
2015-02-10 12:42 UTC, pbradley 		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 pbradley 2015-02-10 12:42:51 UTC 
Build: NetBeans IDE 8.0.2 (Build 201411181905)
VM: Java HotSpot(TM) Client VM, 25.11-b03, Java(TM) SE Runtime Environment, 1.8.0_11-b12
OS: Windows 7

User Comments:
pbradley: Build and deploy of web app

GUEST: OutOfMemoryError: unable to create new native thread




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:714)
   at org.netbeans.modules.web.jspparser_ext.WebAppParseSupport.callTomcatParser(WebAppParseSupport.java:576)
   at org.netbeans.modules.web.jspparser_ext.WebAppParseSupport.analyzePage(WebAppParseSupport.java:471)
   at org.netbeans.modules.web.jspparser.JspParserImpl.analyzePage(JspParserImpl.java:204)
   at org.netbeans.modules.web.core.jsploader.TagLibParseSupport$ParsingRunnable.run(TagLibParseSupport.java:365)
Comment 1 pbradley 2015-02-10 12:42:52 UTC 
Created attachment 151924 [details]
stacktrace
Comment 2 Tomas Hurka 2015-06-25 13:23:39 UTC 
"OutOfMemoryError: unable to create new native thread" does not create heap dump so there is not enough information to diagnose and fix this issue. Dev. builds contain workaround so that heap dump is created (issue #252183). Closing this issue as wontfix for now.