[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [Newsgroup Home]
[news.eclipse.technology.albireo] Re: More tips for the sample code

You can also get the stack traces with the jconsole tool that comes with the JDK (http://java.sun.com/j2se/1.5.0/docs/guide/management/jconsole.html) or by hitting Ctrl-Break (on Windows, running with java.exe as opposed to javaw.exe).

James Peltzer wrote:
Unfortunately I seem the Debugger seems to throw errors whenever I try to
suspend execution.  I have changed my Eclipse version from 3.2.2 to 3.3.1.1
and the issue has gone back into hiding.  I'll try to get more information
to you.

-James

"Gordon Hirsch" <gordon.hirsch@xxxxxxx> wrote in message news:fihg2f$rkr$1@xxxxxxxxxxxxxxxxxxxx
James Peltzer wrote:
Gordon (or anyone),
As you suspected, my workaround for the requestFocus deadlock issue is not a solution 100% of the time. In fact, lately the issue is happening frequently enough to prevent my next software release.


Have you any idea why I might be getting deadlock in WComponentPeer._requestFocus when calling it from the AWT EDT after an invokeLater from the SWT EDT? I could really use some help with this one. Naturally, as with most timing bugs, I don't really have a snipped that I can post.
Could you post stack traces from the deadlocked JVM? They would be extremely helpful in diagnosing what the two EDTs (and possibly other threads) are doing at that point.