Comments on: It’s official: GWT 2.0.0 (with SpeedTracer) http://blog.gerardin.info/archives/617 Java, Agile, the Web and other nice things Sun, 15 Jan 2012 01:56:06 +0000 hourly 1 http://wordpress.org/?v=3.3.1 By: Xavier http://blog.gerardin.info/archives/617/comment-page-1#comment-897 Xavier Wed, 06 Jan 2010 17:16:16 +0000 http://blog.gerardin.info/?p=617#comment-897 Great it worked! I've seen other methods but that failed. Now have to stay on 1.7.1 until safari 4.0.5 gets out! But I can continue on discovering GWT which I find great until now! Thanks Olivier! Great it worked! I’ve seen other methods but that failed. Now have to stay on 1.7.1 until safari 4.0.5 gets out! But I can continue on discovering GWT which I find great until now!

Thanks Olivier!

]]> By: olivier http://blog.gerardin.info/archives/617/comment-page-1#comment-896 olivier Tue, 05 Jan 2010 21:28:55 +0000 http://blog.gerardin.info/?p=617#comment-896 Hi, sure I use GWT with Maven, but this has nothing to do with it.. it's a well known bug that was brought by Safari 4.0.4 update. But all hope is not lost! Your options are: <li>not upgrade to 4.0.4 (too late in your case)</li> <li>downgrade to 4.0.3 (tricky)</li> <li>wait for Apple to fix this in Safari 4.0.5</li> <li>use a fix described<a href="http://gwtgeek.blogspot.com/2009/11/hosted-mode-crashes-after-os-update.html" rel="nofollow">here</a></li> Luckily I was aware of this so I didn't apply the 4.0.4 update. Hi, sure I use GWT with Maven, but this has nothing to do with it.. it’s a well known bug that was brought by Safari 4.0.4 update. But all hope is not lost!
Your options are:

  • not upgrade to 4.0.4 (too late in your case)
  • downgrade to 4.0.3 (tricky)
  • wait for Apple to fix this in Safari 4.0.5
  • use a fix describedhere

    • Luckily I was aware of this so I didn’t apply the 4.0.4 update.

    ]]>         By: Xavier http://blog.gerardin.info/archives/617/comment-page-1#comment-895 Xavier Tue, 05 Jan 2010 15:09:49 +0000 http://blog.gerardin.info/?p=617#comment-895 Hi Olivier, Have you ever tried GWT with Maven? I tried a little project, and it keep crashing when refreshing content of GWT run window (Hosted Mode). It says "Invalid memory access of location...". Any experience of such problem? I'm running on a Mac (OS/X 10.6.2 and Safari 4.0.4). I'm frustrated! Thanks, Xavier Hi Olivier,

    Have you ever tried GWT with Maven? I tried a little project, and it keep crashing when refreshing content of GWT run window (Hosted Mode). It says “Invalid memory access of location…”. Any experience of such problem? I’m running on a Mac (OS/X 10.6.2 and Safari 4.0.4). I’m frustrated!

    Thanks,
    Xavier

    ]]>         By: olivier http://blog.gerardin.info/archives/617/comment-page-1#comment-863 olivier Thu, 10 Dec 2009 08:38:43 +0000 http://blog.gerardin.info/?p=617#comment-863 You're correct... it won't work on the public beta, you need a Chromium build that has extensions enabled (apparently this comes and go...). I used this one: http://build.chromium.org/buildbot/snapshots/chromium-rel-mac/34059. You also need to add the command line flag, which is far less trivial on a Mac than it is on Windows. This is easiest done from a terminal window: -cd to /Applications/Chromium.app/Contents/MacOs -rename Chromium (binary file) to something like Chromium.bin -create an executable script named Chromium that will call the original binary with the added parameter. This is what I used: <code>#!/bin/sh exec /Applications/Chromium.app/Contents/MacOS/Chromium.bin --enable-extension-timeline-api $@</code> -don't forget to chmod +x Chromium -start the patched Chromium -next go to the <a href="http://code.google.com/webtoolkit/speedtracer/get-started.html#downloading" rel="nofollow">speedtracer "getting started" page</a>, and skip to step 3 (or click <a href="https://clients2.google.com/service/update2/crx?response=redirect&x=id%3Dognampngfcbddbfemdapefohjiobgbdl%26uc%26lang%3Den-US" rel="nofollow">this link</a> directly). -accept and few warnings and that's it, speedtracer on mac! You’re correct… it won’t work on the public beta, you need a Chromium build that has extensions enabled (apparently this comes and go…). I used this one: http://build.chromium.org/buildbot/snapshots/chromium-rel-mac/34059.

    You also need to add the command line flag, which is far less trivial on a Mac than it is on Windows. This is easiest done from a terminal window:
    -cd to /Applications/Chromium.app/Contents/MacOs
    -rename Chromium (binary file) to something like Chromium.bin
    -create an executable script named Chromium that will call the original binary with the added parameter. This is what I used:

    #!/bin/sh
    exec /Applications/Chromium.app/Contents/MacOS/Chromium.bin --enable-extension-timeline-api $@

    -don’t forget to chmod +x Chromium
    -start the patched Chromium
    -next go to the speedtracer “getting started” page, and skip to step 3 (or click this link directly).
    -accept and few warnings and that’s it, speedtracer on mac!

    ]]>         By: Elias Mårtenson http://blog.gerardin.info/archives/617/comment-page-1#comment-862 Elias Mårtenson Wed, 09 Dec 2009 23:35:53 +0000 http://blog.gerardin.info/?p=617#comment-862 Speed TRacer works fine on Mac. I saw it in action myself yesterday. It was on a collague's machine, so I don't know if he was using the Chrome beta or the nightly build. Speed TRacer works fine on Mac. I saw it in action myself yesterday. It was on a collague’s machine, so I don’t know if he was using the Chrome beta or the nightly build.

    ]]>