Hi Chris

Do you want me to file a bug report? I haven't had a chance to test it on more than one platform (win7/x86_64)/GWT2.1.1 but its likely that I could test it with Vista X86_64/GWT.2.2 this afternoon PST.

Alan



On 2/28/2011 8:28 AM, Chris Conroy wrote:
Alan,

Thanks for the bug report. This appears to be a Windows specific problem for 
beta 12.

On Sun, Feb 27, 2011 at 8:35 AM, Alan Chaney <[email protected] <mailto:[email protected]>> wrote:



    Hmm, Firefox decided to upgrade my Win 7/64 from B11 to B12 this morning. 
I'm using GWT 2.1.1

    I suspect dev mode is broken in FFB12 (although it was fine in B10 and B11)

    When I try and run with FF in dev (hosted) mode I'm getting

    Exception in thread "Code server for mollychat from Mozilla/5.0 (Windows NT 
6.1; WOW64;
    rv:2.0b12) Gecko/20100101 Firefox/4.0b12 on
    http://127.0.0.1:8888/MollyChat.html?gwt.codesvr=127.0.0.1:9997 @ 
7^GWSIdAe-|p~%Y/"
    com.google.gwt.dev.shell.BrowserChannel$RemoteDeathError: Remote connection 
lost
       at
    
com.google.gwt.dev.shell.BrowserChannelServer.processConnection(BrowserChannelServer.java:521)
       at 
com.google.gwt.dev.shell.BrowserChannelServer.run(BrowserChannelServer.java:352)
       at java.lang.Thread.run(Thread.java:619)
    Caused by: java.net.SocketException: Connection reset by peer: socket write 
error
       at java.net.SocketOutputStream.socketWrite0(Native Method)
       at java.net.SocketOutputStream.socketWrite(SocketOutputStream.java:92)
       at java.net.SocketOutputStream.write(SocketOutputStream.java:136)
       at java.io.BufferedOutputStream.flushBuffer(BufferedOutputStream.java:65)
       at java.io.BufferedOutputStream.flush(BufferedOutputStream.java:123)
       at java.io.DataOutputStream.flush(DataOutputStream.java:106)
       at 
com.google.gwt.dev.shell.BrowserChannel$ReturnMessage.send(BrowserChannel.java:1310)
       at
    
com.google.gwt.dev.shell.BrowserChannelServer.processConnection(BrowserChannelServer.java:518)
       ... 2 more

    but it still works fine in Chrome 11.0.672.2. It also works fine with FFB12 
in production mode.

    Sigh... I suppose this is yet another 'upstream' issue with Mozilla 
changing their plug-in API?

    If someone else can confirm this I'll report a bug.

    Regards

    Alan





--
Alan Chaney
CTO and Founder, Mechnicality, Inc.
www.mechnicality.com

--
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.

Reply via email to