Blocking functions cause client's browser to crash

[Jeff]

Hi All,
I'm wondering if anyone else has run into this issue, or if it's just
me (and it very well may be).

I'm using Socket.IO for a realtime web app. It works great, except if
a blocking function is called (something like alert(), prompt() or
confirm()), and the user doesn't immediately respond to them,
sometimes the browser crashes. I haven't been able to pinpoint
exactly how long you need to wait to respond to get the browser to
crash, but it's roughly between 10-60 seconds.

I'm using Chrome. I've experienced this issue on both Mac OS X, and a
Chromebook. The error message I get when this happens is "Aw,
Snap!" / "Something went wrong while displaying this webpage. To
continue, reload or go to another page".

Anyone else running into this? Any ideas?

[Tomas Huang (冠)]

me2:S

[Jeff]

FWIW, I've posted a bug report here: https://github.com/LearnBoost/socket.io-client/issues/301

On Sep 19, 2:45 pm, Tomas Huang (冠) <huangguan3112...@gmail.com>
wrote:
> me2:S

[NoPyGod]

Did you find a solution? I'm experiencing this problem also.

On Sep 21, 1:10 pm, Jeff <jeffzimmer...@gmail.com> wrote:
> FWIW, I've posted a bug report here:https://github.com/LearnBoost/socket.io-client/issues/301
>
> On Sep 19, 2:45 pm, Tomas Huang (冠) <huangguan3112...@gmail.com>
> wrote:
>
>
>
>
>
>
>
> > me2:S
> > 在 2011-9-20 上午1:57，"Jeff" <jeffzimmer...@gmail.com>写道：
>
> > > Hi All,
> > > I'm wondering if anyone else has run into this issue, or if it's just
> > > me (and it very well may be).
>
> > > I'm using Socket.IO for a realtime web app. It works great, except if

> > > a blocking function is called (something likealert(), prompt() or

> > > confirm()), and the user doesn't immediately respond to them,
> > > sometimes the browser crashes. I haven't been able to pinpoint
> > > exactly how long you need to wait to respond to get the browser to
> > >crash, but it's roughly between 10-60 seconds.
>

> > > I'm usingChrome. I've experienced this issue on both Mac OS X, and a

[NoPyGod]

Reported it on the Chromium discussion group

http://groups.google.com/a/chromium.org/group/chromium-discuss/browse_thread/thread/dfc65779f762d935#

[NoPyGod]

My apologies, I had left out a crucial detail. The server is actually
immediately disconnecting the client after sending the 'na' message -

fn({ok: 'na', msg: e});
socket.disconnect();

So the crash only occurs if the server disconnects the client right
after it sends the message

On Sep 28, 11:50 pm, NoPyGod <nopy...@gmail.com> wrote:
> Reported it on the Chromium discussion group
>

> http://groups.google.com/a/chromium.org/group/chromium-discuss/browse...

[NoPyGod]

Reported here

https://github.com/LearnBoost/socket.io-client/issues/312

On Sep 28, 11:50 pm, NoPyGod <nopy...@gmail.com> wrote:

> Reported it on the Chromium discussion group
>

> http://groups.google.com/a/chromium.org/group/chromium-discuss/browse...

[Jeff]

@NoPyGod: sorry, I just saw your question. I did not find a solution
yet. One more data point... when I experienced this issue, there was
no Socket.disconnect() call. Is it possible that the alert/prompt/
confirm held up the browser, and the browser disconnected, causing the
crash?

[Jeff]

Just an update...
I've filed a bug report with the Chromium team. You can find it here:
http://code.google.com/p/chromium/issues/detail?id=101187&thanks=101187&ts=1319223714