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 30300 - IDE hangs while using Auto Comment tool
Summary: IDE hangs while using Auto Comment tool
Status: CLOSED DUPLICATE of bug 30464
Alias: None
Product: platform
Classification: Unclassified
Component: -- Other -- (show other bugs)
Version: 3.x
Hardware: PC Windows XP
: P3 blocker (vote)
Assignee: Petr Nejedly
URL:
Keywords: THREAD
: 30299 (view as bug list)
Depends on:
Blocks:
 
Reported: 2003-01-23 08:13 UTC by tboerkel
Modified: 2008-12-22 16:33 UTC (History)
1 user (show)

See Also:
Issue Type: DEFECT
Exception Reporter:

Attachments
ThreadDump (18.42 KB, text/plain)
2003-01-23 08:15 UTC, tboerkel 		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 tboerkel 2003-01-23 08:13:08 UTC 
While this happened in the Auto Comment tool, I somehow 
don't think it is its fault. See also issue #30299.
Using NB 3.4.1 with JDK 1.4.1_01.
Attaching ThreadDump.
Comment 1 tboerkel 2003-01-23 08:15:40 UTC 
Created attachment 8653 [details]
ThreadDump
Comment 2 pzajac 2003-01-23 09:01:41 UTC 
That seems like problem in JVM Thread is waiting on monitor entry for 
at 

"AWT-EventQueue-0" prio=7 tid=0x0FE698E0 nid=0x94c waiting for monitor
entry [135df000..135dfd8c]
        at java.lang.StringBuffer.<init>(StringBuffer.java:115)
        at
org.openide.filesystems.AbstractFolder.getPackageNameExt(AbstractFolder.java:167)


Can you reproduce it?
Comment 3 pzajac 2003-01-23 09:02:13 UTC 
*** Issue 30299 has been marked as a duplicate of this issue. ***
Comment 4 tboerkel 2003-01-23 09:48:59 UTC 
It's not exactly reproducable. It just hangs after working 
much in a relatively short time. We have at least one 
additional machine where it also happens. I am waiting for 
a thread dump from that one.
Is it possible that this is a Java2D problem?
Comment 5 pzajac 2003-01-29 15:55:35 UTC 
P Nejedly, please evaluate this bug.
Comment 6 Petr Nejedly 2003-01-31 13:09:19 UTC 
Both this and issue #30299 seem to me like some problem in JVM. In
both dumps, several threads are
waiting for new char[] or some other allocation
to happen. Like if the JVM internal heap allocator
mutex went crazy...
Comment 7 tboerkel 2003-01-31 13:15:00 UTC 
Maybe this is related to issue #30464?
Comment 8 pzajac 2003-01-31 14:38:06 UTC 
yes duplicate of #30464

*** This issue has been marked as a duplicate of 30464 ***
Comment 9 Quality Engineering 2003-07-01 15:46:00 UTC 
Resolved for 3.4.x or earlier, no new info since then -> verified.
Comment 10 Quality Engineering 2003-07-01 16:24:48 UTC 
Resolved for 3.4.x or earlier, no new info since then -> closing.