My local tests started failing soon after upgrading my machine to Safari 4.0.4. Some research and pointers from the GWT folk pointed me at the root cause, a WebKit bug which is now fixed.

Kelly Norton pointed me at a quick fix:

1. Download the latest WebKit nightly from here
2. Save it locally
3. Add the following environment variable to your testing .launch targets (using the path to your new WebKit.app, of course). Tests run from Ant or the command line will need to use the appropriate tasks or shell commands:

   Name: DYLD_FRAMEWORK_PATH
   Value: /Applications/path-to-your-local-webkit/WebKit.app/Contents/Frameworks/10.5
   

4. Snow Leopard users will need to use 10.6 in the path above.

The proper fix should arrive in WebKit 4.0.5 at some point, but this will keep you running for now.

Jim Douglas has posted more detailed instructions on how to configure your launch targets on the GWT issue here: Issue #4220: GWT crash (Safari 4.0.4)

This entry was posted on Monday, November 16th, 2009 at 10:31 pm and is filed under development, gwt, java. You can follow any responses to this entry through the RSS 2.0 feed. You can leave a response, or trackback from your own site.