Comment 11 for bug 532550

I know Andrew said "let's not guess" which is generally a good idea ... but I'm still going to guess that the server is sending error messages onto the socket. Didn't mwh recently fix a similar bug?