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 174618 - [68cat] Apparent deadlock
Summary: [68cat] Apparent deadlock
Status: RESOLVED DUPLICATE of bug 174408
Alias: None
Product: editor
Classification: Unclassified
Component: -- Other -- (show other bugs)
Version: 6.x
Hardware: PC Linux
: P1 blocker (vote)
Assignee: issues@editor
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-10-15 09:05 UTC by dynamite
Modified: 2009-10-15 11:03 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:

Attachments
thread dump (31.33 KB, text/plain)
2009-10-15 09:08 UTC, dynamite 		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 dynamite 2009-10-15 09:05:44 UTC 
[ BUILD # : 200910140201 ]
[ JDK VERSION : 1.6.* ]

Created a new Groovy file and cut-and-paste a few things in.  I then
try to edit it, but the IDE doesn't respond.  I bring up konsole and
then minimise and note that the IDE isn't redrawing.  I then get a
thread dump which I attach.
Comment 1 dynamite 2009-10-15 09:08:58 UTC 
Created attachment 89507 [details]
thread dump
Comment 2 dynamite 2009-10-15 09:38:54 UTC 
I've been hit by this twice in succession today after only a small amount of IDE use.  I didn't have this problem with
200910100201.  Looks like the XSLT debugger plug-in is involved and so I am now removing this and restarting.  I should
note that that this plug-in was installed in 200910100201 and I didn't experience this issue.
Comment 3 Petr Hejl 2009-10-15 10:08:33 UTC 
Looks like deadlock between CloneableEditor and AWTTreeLock...

No groovy code in thread dump.
Comment 4 dynamite 2009-10-15 10:35:35 UTC 
200910140201 seems stable now that the xslt debugger has been removed.  It is a bit disturbing that this was causing
trouble as I had no xslt file open.  I guess the question is whether the xslt debugger module is doing something invalid
or whether it is just able to prevoke a deadlock that could occur more generally.
Comment 5 Vitezslav Stejskal 2009-10-15 11:03:30 UTC 
Unrelated to xslt debugger or groovy editor.

*** This issue has been marked as a duplicate of 174408 ***