Bugs item #1735260, was opened at 2007-06-11 11:50
Message generated for change (Comment added) made by ezust
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=100588&aid=1735260&group_id=588
Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: editor core
Group: severe bug
>Status: Deleted
>Resolution: Out of Date
Priority: 5
Private: No
Submitted By: Charles Kennedy (charles_kennedy)
Assigned to: Nobody/Anonymous (nobody)
Summary: jedit hangs in File System Browser
Initial Comment:
Jedit frequently hangs on me when using the File System Browser under Fedora Core 6. Attached is a "full thread dump".
----------------------------------------------------------------------
>Comment By: Alan Ezust (ezust)
Date: 2007-08-20 09:36
Message:
Logged In: YES
user_id=935841
Originator: NO
egads, 4.1final? That's sooo old.
I'd prefer if you would use 4.3pre10 instead of 4.2final, since you
already went through the trouble of getting an account on sf.net to report
bugs. We only fix bugs in 4.3preXX, so there's no point in reporting bugs
against an older version.
----------------------------------------------------------------------
Comment By: Charles Kennedy (charles_kennedy)
Date: 2007-08-20 09:30
Message:
Logged In: YES
user_id=568075
Originator: YES
I'm running version 4.1final. I don't remember exactly when I downloaded
jedit, but I reformatted and installed Fedora Core 6 last November, so I
know it's been since that date.
Anyway, I'll withdraw the bug and try 4.2final. (Or is 4.3 stable enough
for everyday use?)
----------------------------------------------------------------------
Comment By: Marcelo Vanzin (vanza)
Date: 2007-08-18 11:28
Message:
Logged In: YES
user_id=75113
Originator: NO
Charles,
I'm looking at the code and the stack traces you're seeing are just not
possible in the current (or any recent version). Looking at this snippet:
at java.awt.Component.setCursor(Unknown Source)
at
org.gjt.sp.jedit.browser.VFSFileChooserDialog$WorkThreadHandler.statusUpdate(Unknown
Source)
- locked <0x896fbb80> (a
org.gjt.sp.jedit.browser.VFSFileChooserDialog)
That trace is only possible in revision #4167, which is *ancient* (I won't
try to guess which version, but it was fixed in 2003). Which jEdit version
are you using?
----------------------------------------------------------------------
Comment By: Marcelo Vanzin (vanza)
Date: 2007-08-18 11:10
Message:
Logged In: YES
user_id=75113
Originator: NO
Another interesting thing about this stack trace is that the I/O thread is
executing AWT methods, which is Bad (tm), and could end up causing things
like the buffer corruption problem some people have seen.
"jEdit I/O #1":
at java.awt.Container.findComponentAt(Unknown Source)
- waiting to lock <0x89493a20> (a java.awt.Component$AWTTreeLock)
at sun.awt.X11.XGlobalCursorManager.findComponentAt(Unknown
Source)
at sun.awt.GlobalCursorManager._updateCursor(Unknown Source)
at sun.awt.GlobalCursorManager.updateCursorImmediately(Unknown
Source)
at sun.awt.X11.XComponentPeer.updateCursorImmediately(Unknown
Source)
...
----------------------------------------------------------------------
Comment By: Charles Kennedy (charles_kennedy)
Date: 2007-07-23 14:43
Message:
Logged In: YES
user_id=568075
Originator: YES
I have rarely gotten through an editing session without a hang under
Linux--hence I've not used jedit much under Linux due to this problem. (I
have used it with greater success under Solaris.)
I'm using jedit today to try and capture additional details. It hung
after I opened the File System Browser, navigated to a different directory,
then double clicked on the desired filename. A few minutes earlier I had
done the same thing without a problem. The visible symptom is that the
File System Browser window gets erased after double clicking on the
filename, but nothing replaces it--i.e., you see a gray square where it had
been.
Sometimes I can use the browser several times before this happens, but
frequently it occurs on the 1st or 2nd time I attempt to use it. (I have
never seen this problem when opening additional files from the command
line.)
----------------------------------------------------------------------
Comment By: Alan Ezust (ezust)
Date: 2007-07-19 18:42
Message:
Logged In: YES
user_id=935841
Originator: NO
I am looking at the stack trace now. Interesting.
Do you have steps to reproduce?
I just want to quote one part of the attached file to this description:
Found one Java-level deadlock:
=============================
"jEdit I/O #1":
waiting to lock monitor 0x09f2084c (object 0x89493a20, a
java.awt.Component$AWTTreeLock),
which is held by "AWT-EventQueue-0"
"AWT-EventQueue-0":
waiting to lock monitor 0x09f2088c (object 0x896fbb80, a
org.gjt.sp.jedit.browser.VFSFileChooserDialog),
which is held by "jEdit I/O #1"
----------------------------------------------------------------------
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=100588&aid=1735260&group_id=588
|