Right, but I'm launching OOPHM using command line Ant... Not from
Eclipse. I was just confused... I thought that launching OOPHM using
command line Ant would not helpfully add the -XstartOnFirstThread
flag. But running ant with the -v switch tells the real story:
oophm:
[java] Executing
'/System/Library/Frameworks/JavaVM.framework/Versions/1.5.0/Home/bin/java'
with arguments:
[java] '-Xmx256M'
[java] '-XstartOnFirstThread'
[java] '-classpath'
Thanks again John!
On Wed, Jul 8, 2009 at 12:56 PM, John Tamplin<[email protected]> wrote:
> On Wed, Jul 8, 2009 at 3:37 PM, Aaron Steele <[email protected]> wrote:
>>
>> I'm having a strange problem with trunk (r5690) where the OOPHM Swing
>> UI is freezing on Mac OS X 10.5.7 with the Safari 4 plugin.
>>
>> The easiest way to reproduce the problem:
>>
>> 1) Compile trunk (via `ant build`) with 32-bit Java 1.5
>> 2) Create new app via `webAppCreator foo.Bar`
>> 3) Run `ant oophm`
>>
>> Here's the output from 3 above:
>>
>> libs:
>> javac:
>> oophm:
>> [java] 2009-07-08 12:22:27.590 java[4630:80f] [Java
>> CocoaComponent compatibility mode]: Enabled
>> [java] 2009-07-08 12:22:27.592 java[4630:80f] [Java
>> CocoaComponent compatibility mode]: Setting timeout for SWT to
>> 0.100000
>> [java] 2009-07-08 12:22:28.150 java[4630:17403] ***
>> -[NSConditionLock unlock]: lock (<NSConditionLock: 0x17af10> '(null)')
>> unlocked when not locked
>> [java] 2009-07-08 12:22:28.151 java[4630:17403] *** Break on
>> _NSLockError() to debug.
>> [java] 2009-07-08 12:22:28.258 java[4630:17403] ***
>> -[NSConditionLock unlock]: lock (<NSConditionLock: 0x18f0b0> '(null)')
>> unlocked when not locked
>> [java] 2009-07-08 12:22:28.259 java[4630:17403] *** Break on
>> _NSLockError() to debug.
>> [java] 2009-07-08 12:22:28.372 java[4630:17403] ***
>> -[NSConditionLock unlock]: lock (<NSConditionLock: 0x190400> '(null)')
>> unlocked when not locked
>> [java] 2009-07-08 12:22:28.372 java[4630:17403] *** Break on
>> _NSLockError() to debug.
>> [java] 2009-07-08 12:22:28.474 java[4630:17403] ***
>> -[NSConditionLock unlock]: lock (<NSConditionLock: 0x1903e0> '(null)')
>> unlocked when not locked
>> [java] 2009-07-08 12:22:28.474 java[4630:17403] *** Break on
>> _NSLockError() to debug.
>> [java] 2009-07-08 12:22:28.612 java[4630:17403] ***
>> -[NSConditionLock unlock]: lock (<NSConditionLock: 0x192db0> '(null)')
>> unlocked when not locked
>> [java] 2009-07-08 12:22:28.613 java[4630:17403] *** Break on
>> _NSLockError() to debug.
>> [java] 2009-07-08 12:22:29.503 java[4630:17403] ***
>> -[NSConditionLock unlock]: lock (<NSConditionLock: 0x195d40> '(null)')
>> unlocked when not locked
>> [java] 2009-07-08 12:22:29.504 java[4630:17403] *** Break on
>> _NSLockError() to debug.
>>
>> The Swing UI launches but immediately freezes (i.e. it's un-clickable
>> and won't accept focus). See the attached screen shot. If I access the
>> the app using the address in the Swing UI via Safari, it works, and
>> the UI updates with a message that a connection was received. The
>> Swing UI is still frozen though. If I try running OOPHM through
>> Eclipse, the Swing UI doesn't launch at all.
>
> See the UsingOOPHM wiki page and the instructions on using Eclipse on the
> mac. The problem is that Eclipse helpfully adds -XstartOnFirstThread (which
> is necessary for SWT apps running on the Apple JVM) if it sees the SWT jars
> on your classpath, yet that flag breaks all Swing apps. So, you have to
> open the gwt-dev-mac project and remove the SWT jars from there for OOPHM to
> work.
>
> --
> John A. Tamplin
> Software Engineer (GWT), Google
>
> >
>
--~--~---------~--~----~------------~-------~--~----~
http://groups.google.com/group/Google-Web-Toolkit-Contributors
-~----------~----~----~----~------~----~------~--~---
