Re: [platform-swt-dev] SWT_AWT on Mac, first impressions

[Scott Kovatch <skovatch@xxxxxxxxx>]

On Oct 1, 2009, at 2:11 PM, Christopher Deckers wrote:

"Thread-0" daemon prio=5 tid=0x0000000101848000 nid=0x7fff7062c700

runnable [0x00007fff5fbfa000]

  java.lang.Thread.State: RUNNABLE

       at apple.awt.CToolkit.doAWTRunLoop(Native Method)

       at apple.awt.CToolkit.invokeAndWait(CToolkit.java:1112)

       at apple.awt.CToolkit.invokeAndWait(CToolkit.java:1093)

       at apple.awt.ComponentModel.handlePaint(ComponentModel.java:323)

       at org.eclipse.swt.internal.cocoa.OS.objc_msgSendSuper(Native Method)

       at org.eclipse.swt.widgets.Display.applicationSendEvent(Display.java:4349)

       at org.eclipse.swt.widgets.Display.applicationProc(Display.java:4426)

       at org.eclipse.swt.internal.cocoa.OS.objc_msgSend(Native Method)

       at org.eclipse.swt.internal.cocoa.NSApplication.sendEvent(NSApplication.java:101)

       at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3159)

There is also this one that seems to be waiting forevent when our AWT
thread is syncExec:

"Thread-0" daemon prio=5 tid=0x0000000101848000 nid=0x7fff7062c700
runnable [0x00007fff5fbfd000]
  java.lang.Thread.State: RUNNABLE
at org.eclipse.swt.internal.cocoa.OS.objc_msgSend_bool(Native Method)
at org.eclipse.swt.internal.cocoa.NSRunLoop.runMode(NSRunLoop.java:42)
at org.eclipse.swt.widgets.Display.sleep(Display.java:3967)

This one does not have clear AWT indication, but could it be related?
What do you think?

I will have to talk to the AWT guys at Apple about this. The AWT occasionally runs in a special mode to guard against deadlocks, and normally the host application shouldn't need to worry about it. (The SWT is considered a 'host application' in this case), but SWT/AWT interaction may be triggering something new that would require us to make a change.

-- Scott

----------

Scott Kovatch

Flex Engineering

skovatch@xxxxxxxxx

I am Scott Kovatch, and I approve this message.