Hmm. Ok, I think I have a vague idea what's happening, but I don't know why. When I start my GWT Web App from Eclipse, the command line includes -XstartOnFirstThread. If I copy that entire command line and run it from a command shell -- but omit -XstartOnFirstThread -- then those errors go away, and some strange application problems that I've been trying to track down also go away.
So the next question is -- why would the GWT Eclipse Plugin be setting that flag, and how can I convince it to stop? I see references to it here: http://code.google.com/p/google-web-toolkit/wiki/UsingOOPHM But I don't see how to disable that option. On Dec 16, 12:28 pm, Jim Douglas <[email protected]> wrote: > GWT 2.0 seems to be working ok here, but I've been noticing floods of > these error messages in the console: > > 2009-12-16 12:17:55.552 java[25151:13b03] *** -[NSConditionLock > unlock]: lock (<NSConditionLock: 0x143e511a0> '(null)') unlocked when > not locked > 2009-12-16 12:17:55.553 java[25151:13b03] *** Break on _NSLockError() > to debug. > > Does anyone know what that means, and what I should do about it? -- You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
