Hello, Viral.
It's known that there are some deadlocks in SWT_AWT bridge on Mac. Here's an
example:
https://bugs.openjdk.java.net/browse/JDK-8020165
It would be useful if you also post the dump of an Appkit thread to identify
your particular case.
The deadlock occurs because AWT is called on t
Oh, I apologize. the poor formatting of my email client caused me to
misread your code sample.
On Mon, Nov 18, 2013 at 3:01 PM, Viral Barot wrote:
> I am calling the invokeAndWait from Main thread.
>
> On Nov 18, 2013, at 2:58 PM, Mike Murray
> wrote:
>
> This is a developer error. You can
I am calling the invokeAndWait from Main thread.
On Nov 18, 2013, at 2:58 PM, Mike Murray
mailto:ashesf...@gmail.com>>
wrote:
This is a developer error. You can't call invoke and wait from an event method
because invoke and wait puts your new runnable on the queue but since you are
waiting fr
This is a developer error. You can't call invoke and wait from an event
method because invoke and wait puts your new runnable on the queue but
since you are waiting from the queue itself it hangs. You need to comb your
codebase and deal with this issue. These invoke methods are to be used
outside t
Accessing AWT frame from a thread causes the application to freeze when
executed with JRE 7. The AWT frame is created with SWT_AWT bridge.
Below is the test case in which call to frame.setVisible(true); from the AWT
event dispatching thread does not return.
Test Case:
import java.awt.Button;
im
