Sockets bug in Chrome: all profiles seem to use the same sockets space about uproxy-p2p HOT 5 CLOSED

Comment by infmally from Wed Oct 9 04:01:37 2013

More details:

We also finally found the long-standing hideous monster bug in XMPP that we thought for a long time (wrongly) was just a login problem. Here's how to make it happen and see the monstrosity:
3 accounts: A, B, C (which each other as buddies)

1. login on A on a stable third party XMPP client, such as pidgin
2. reload the app to auto-login on B in uproxy.
3. reload the app to auto-login on C in uproxy.

Observe, using A, that B just disconnected form XMPP! And: observe that no output happens in the background page for B. The socket connection got terminated without any event being raised.

Reload the app in B. Observe, using A, that C got disconnected, but C knew nothing about it.

This has been a mega-source of pain and confusion and unreliability; however, we now have at least this beast in our sights! @mollyling is hunting the critter down...

from uproxy-p2p.

Comment by mollyling from Wed Oct 9 20:56:09 2013

From a 3rd party observer, if the two uproxy clients aren't on the same machine, it doesn't seem like you have to log in twice.

from uproxy-p2p.

Comment by infmally from Fri Dec 6 02:54:55 2013

Looks like this is a bug in Chrome's handling of sockets. It seems to try and re-use the same socket in different profiles. We should figure out what's happening and fit it in chrome.

from uproxy-p2p.

Comment by scouttle from Wed Apr 16 20:30:41 2014

(Context: probably not a problem for us, unless the user is using uProxy on multiple Chrome profiles at once.)

from uproxy-p2p.

This seems to have been solved a while ago, closing

from uproxy-p2p.