race-condition? chrome websocket 'aw-snap'

[chrisdew]

Ubuntu 10.04 x86_64, Chrome 5.0.375.86, latest Socket.IO and Socket.IO-node (git pulled 2 minutes ago).

If I send data in a socket.addListener "clientConnect" function, the behaviour is non-deterministic.

I'm using the demo client and slightly-modified server (it just sends data on client connect).

On many occasions the browser shows "got some data: {"sessionid":"19619322172366083"}" (i.e. the connection handshake is escaping to the application layer)
On other occasions it shows the data the server has sent, sometimes multiple times for a single sending.

After 2-4 of the events above, Chrome goes 'aw-snap'.

If I only send data from the server after data has been received from the client, everything is fine.

Also everything is fine if I use xhr.

Regards,

Chris.

[erdemgezer]

I'm having the same problem with you. Have you found any solutions?

[erdemgezer]

Ok, I found it !
An alert function in clientConnect event kills the Chrome.

[rauchg]

Nofix