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 18478 - out of memory error on compilation of package
Summary: out of memory error on compilation of package
Status: CLOSED WORKSFORME
Alias: None
Product: java
Classification: Unclassified
Component: Unsupported (show other bugs)
Version: 3.x
Hardware: Other Other
: P3 blocker (vote)
Assignee: issues@java
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2001-12-08 18:41 UTC by Dennis Daniels
Modified: 2007-09-26 09:14 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments
ide log (330.75 KB, text/plain)
2001-12-08 18:42 UTC, Dennis Daniels
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Dennis Daniels 2001-12-08 18:41:34 UTC
Sat Dec 08 19:37:55 CET 2001: java.lang.OutOfMemoryError: unable to create new 
native thread
java.lang.OutOfMemoryError: unable to create new native thread
        at java.lang.Thread.start(Native Method)
        at 
org.netbeans.core.compiler.CompilationEngineImpl$CompilerThread$GroupCompiler.<i
nit>(CompilationEngineImpl.java:236)
[catch] at org.netbeans.core.compiler.CompilationEngineImpl$CompilerThread.run
(CompilationEngineImpl.java:198)
Comment 1 Dennis Daniels 2001-12-08 18:42:36 UTC
Created attachment 3744 [details]
ide log
Comment 2 Svata Dedic 2001-12-10 13:57:04 UTC
The OOM condition is not created by compilation - external compiler is
being used, so no potential memory leaks in the internal one
contribute to the situation. Looking at the entire log, the problem
may lie in extensive usage of clazz module's features, which (because
it is implemented through reflection) may overfill HotSpot's area for
reflective information. This is already solved in 3.3 release.
Comment 3 Quality Engineering 2003-07-01 13:11:18 UTC
Resolved for 3.3.x or earlier, no new info since then -> closing.
Comment 4 Quality Engineering 2003-07-01 13:19:16 UTC
Resolved for 3.4.x or earlier, no new info since then -> closing.