Cocoa AWT: Not running on AppKit thread 0 when expected.
Michael Hall
mik3hall at gmail.com
Sat Oct 22 16:53:21 PDT 2011
011-10-22 18:08:21.303 java[278:8707] Cocoa AWT: Not running on AppKit thread 0 when expected. (
0 liblwawt.dylib 0x16da9ce4 +[ThreadUtilities getJNIEnv] + 46
1 liblwawt.dylib 0x16d9392f -[CDragSource init:component:peer:control:transferable:triggerEvent:dragPosX:dragPosY:modifiers:clickCount:timeStamp:cursor:dragImage:dragImageOffsetX:dragImageOffsetY:sourceActions:formats:formatMap:] + 101
2 liblwawt.dylib 0x16d93d98 Java_sun_lwawt_macosx_CDragSourceContextPeer_createNativeDragSource + 767
3 ??? 0x02491e0a 0x0 + 38346250
4 ??? 0x0248a404 0x0 + 38315012
)
2011-10-22 18:08:21.347 java[278:8707] Please file a bug report at http://java.net/jira/browse/MACOSX_PORT with this message and a reproducible test case.
There appear to be a couple issues open with this error message although they don't appear to concern drag and drop in a text component.
I believe I've also seen there are currently known issues concerning drag and drop.
(Incidentally I wasn't trying to drag and drop, just select some text for copying).
Should I bug report?
I am using Eclipse which I normally don't. Should I use some start on main thread jvm arg? I seem to remember this was recommended for launching in some situations, if not all? Does this possibly just mean I'm not running on the EDT when I should be?
More information about the macosx-port-dev
mailing list