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 95515 - Deadlock in editor while debugging
Summary: Deadlock in editor while debugging
Status: RESOLVED INVALID
Alias: None
Product: xml
Classification: Unclassified
Component: XAM (show other bugs)
Version: 6.x
Hardware: All All
: P4 blocker (vote)
Assignee: Samaresh Panda
URL:
Keywords: RANDOM
Depends on:
Blocks:
 
Reported: 2007-02-14 09:42 UTC by Jan Becicka
Modified: 2009-02-19 23:31 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:

Attachments
Full thread dump (13.81 KB, text/plain)
2007-02-14 09:43 UTC, Jan Becicka 		Details
Fragment of thread dump (5.58 KB, text/plain)
2007-04-12 14:52 UTC, Nikita Krjukov 		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 Jan Becicka 2007-02-14 09:42:31 UTC 
or in debugger while editing?
Product Version         = NetBeans IDE Dev (Build 070115)
Operating System        = Windows XP version 5.1 running on x86
Java; VM; Vendor; Home  = 1.6.0-rc; Java HotSpot(TM) Client VM 1.6.0-rc-b97;
Comment 1 Jan Becicka 2007-02-14 09:43:16 UTC 
Created attachment 38476 [details]
Full thread dump
Comment 2 Vitezslav Stejskal 2007-02-14 10:29:46 UTC 
This one is quite interesting. The AWT is waiting for the write lock on
JavaDocument, but no other threads seem to hold its read or write lock. I think
that some code locked the document and forgot to unlock it. Is this situation
reproducible?
Comment 3 Jan Becicka 2007-02-14 12:18:17 UTC 
Of course not reproducible :)
I let the IDE open attached to another instance of NetBeans doing some debugging
for a while. I need to join some meeting, when I returned back I wanted to
continue  debugging, but the IDE was frozen.
Comment 4 Nikita Krjukov 2007-04-12 14:50:35 UTC 
I've faced the same problem at least twice. 
Now I've decided to look for the issue and it seems here it is. 

The problem has happened always in debug mode. I edited an XML file and the 
NetBeans was locked after I copy & paste a part of text. 

It seems really difficult to find out the true reason :-( 
Just to help I tried to look over all NetBeans code and found the following 
methods a bit suspicious: 
   org.netbeans.modules.editor.fold.FoldHierarchyExecution.rebuild();
   org.netbeans.editor.DrawEngine.draw(8 params);
Comment 5 Nikita Krjukov 2007-04-12 14:52:58 UTC 
Created attachment 40826 [details]
Fragment of thread dump
Comment 6 Vitezslav Stejskal 2007-04-12 23:29:54 UTC 
I am not sure that these two reports are the same (the one from jbecicka and the
other one from supernikita), but the thread dump from supernikita looks like a
problem in XAM module.
Comment 7 tonybeckham 2007-06-14 20:39:11 UTC 
Unable to reproduce.

System Info:
Product Version: NetBeans IDE Dev (Build 200706131200) 
Java: 1.5.0_07; Java HotSpot(TM) Client VM 1.5.0_07-87 
System: Mac OS X version 10.4.9 running on i386; MacRoman; en_US (nb)

Maybe keeping an eye in this is best since the exact steps to reproduce are vague.  I'm going to change the priority to P4.
Comment 8 Samaresh Panda 2008-12-04 16:48:29 UTC 
I'm surprised to find deadlock as a P4. Should be invalid. Please open new issues as P1/P2 if you encounter something
like this.