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.
Summary: | Hundreds of JavaFastOpen.Evaluator threads left in VM | ||
---|---|---|---|
Product: | editor | Reporter: | Jesse Glick <jglick> |
Component: | -- Other -- | Assignee: | issues@editor <issues> |
Status: | RESOLVED FIXED | ||
Severity: | blocker | CC: | issues, phrebejk, pnejedly |
Priority: | P2 | Keywords: | PERFORMANCE |
Version: | 3.x | ||
Hardware: | PC | ||
OS: | Linux | ||
Issue Type: | DEFECT | Exception Reporter: | |
Attachments: |
Java code snippet
Sample output |
Description
Jesse Glick
2003-10-02 01:59:14 UTC
Created attachment 11767 [details]
Java code snippet
Created attachment 11768 [details]
Sample output
Hint: try to avoid creating Thread's you don't plan to ever start() (as I see is done in some places with SwingUtilities here). ThreadGroup seems to have a bug about unstarted threads. Just make a Runnable and post it instead. BTW I will escalate: http://developer.java.sun.com/developer/bugParade/bugs/4533087.html This appears to be fixed in tiger-beta but we will try to avoid the threads that never run anyway into 3.6. *** Issue 44771 has been marked as a duplicate of this issue. *** OK, but please keep the relevant attributes and copy cc-ers. Not only threads are left but it can also cause moderate memory leak. Fixed in trunk: Checking in libsrc/org/netbeans/editor/ext/java/JavaFastOpen.java; /cvs/editor/libsrc/org/netbeans/editor/ext/java/JavaFastOpen.java,v <-- JavaFastOpen.java new revision: 1.21; previous revision: 1.20 Jesse, could You please verify this issue? Thanks. |