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 68257 - deadlock while editing.
Summary: deadlock while editing.
Status: RESOLVED FIXED
Alias: None
Product: java
Classification: Unclassified
Component: Unsupported (show other bugs)
Version: 5.x
Hardware: All All
: P3 blocker (vote)
Assignee: Jan Becicka
URL:
Keywords:
: 68301 (view as bug list)
Depends on:
Blocks:
 
Reported: 2005-11-08 05:46 UTC by _ pcw
Modified: 2007-09-26 09:14 UTC (History)
1 user (show)

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments
Deadlock thread dump. (17.56 KB, text/plain)
2005-11-08 05:47 UTC, _ pcw
Details

Note You need to log in before you can comment on or make changes to this bug.
Description _ pcw 2005-11-08 05:46:15 UTC
This was with 5.0 Beta (First one).

I was editing a class in the editor, doing some cutting and pasting across some
files for manual refactoring I needed to do and the editor deadlocked (or went
into an infinite loop and also can't paint, so that's kind of the same thing.)

This is on a 2 CPU machine and the java VM has maxed out BOTH CPU's.  The system
is only a 2xPIII/600 so it's a bit slow and the editor features (code
completion, error parsing, etc) were having trouble keeping up with my typing
and pasting as well.

Before this happened, the following text is repeated about 30 times in the
console window:  "Exception in Listener.change () thrown !!", but no exception
traces are shown.

Thread dump is attached.
Comment 1 _ pcw 2005-11-08 05:47:07 UTC
Created attachment 26693 [details]
Deadlock thread dump.
Comment 2 Martin Roskanin 2005-11-08 08:44:44 UTC
MDR transaction from AWT, reassigning to java module
Comment 3 Jan Becicka 2005-11-08 09:09:38 UTC
Checking in JavaEditor.java;
/cvs/java/src/org/netbeans/modules/java/JavaEditor.java,v  <--  JavaEditor.java
new revision: 1.204; previous revision: 1.203
done
Comment 4 Dusan Balek 2005-11-09 07:43:05 UTC
*** Issue 68301 has been marked as a duplicate of this issue. ***