> > Yeah it is a deadlock: http://pastebin.com/WCVZc21E >> > > Hmm although it is not a java level dead lock. Seems like GWT can not > close a jar file? Strange. >
Ok we just solved it. The Java run configuration had a VM parameter "-XstartOnFirstThread" and when removing it the CodeServer works as expected. The colleague copied that parameter from his classic DevMode "Web Application" run configuration. It seems like that Eclipse adds this parameter automatically on Mac OS when creating a new "Web Application" run configuration (provided by GPE). That means most DevMode run configurations have that parameter set. This might affect the new -superDevMode feature of GWT 2.7 as well. Maybe you can try to reproduce the issue by using Mac OS and adding the VM parameter "-XstartOnFirstThread" to "CodeServer" and "DevMode -superDevMode". We attached a debugger to CodeServer and the thread that hangs wants to close an input stream of the jar url connection gwt-user.jar!/.../disclosurePanelClosed.png. So to reproduce it your demo project should probably use a DisclosurePanel. If you can reproduce it, it might be a good idea to mention that behavior for Mac OS users in the 2.7 release notes. -- J. -- You received this message because you are subscribed to the Google Groups "GWT Contributors" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/google-web-toolkit-contributors/e0986157-9395-4f0d-ae01-d4e3a001bf2b%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
