Browser infinite loop issue

[LivInTheLookingGlass]

To reproduce:

Construct a node in node.js like:

let js2p = require('./js_src/js2p.js');
let conn = new js2p.mesh.mesh_socket('localhost', 4444, new js2p.base.protocol('test', 'ws'));

Create and connect node in Firefox using:

let conn = new js2p.mesh.mesh_socket(null, null, new js2p.base.protocol('test', 'ws'));
conn.connect('localhost', 4444);

Watch everything break

[LivInTheLookingGlass]

This appears to be from the inclusion of zlibjs. I'm not sure why the compression is making things fail, though. All other issues are fixed thus far. I will try this again momentarily.

[LivInTheLookingGlass]

Still present. Still only occurs when zlibjs is included. Not sure what's going on, nor how to debug it, since Firefox dies every time I get a connection.

[LivInTheLookingGlass]

Thought: Does this also happen when talking from a websocket server to another? Or, for that matter, on chromium?

[LivInTheLookingGlass]

On chromium errors continuously pile up. It looks like it's trying to disconnect, but failing. It crashed chromium after building up ~15000 errors. The server node noticed nothing at all.

[LivInTheLookingGlass]

As a sidenote, browser error handling seems to be disabled, since it currently relies on the socket emit function. Things will get easier to fix once that is corrected.

[LivInTheLookingGlass]

Okay, the error is caused by (depending on viewpoint):

1. The server erroneously sending a compressed message
2. The receiver erroneously deciding the message wasn't compressed.

When you manually set the compression methods to the real list, everything works again. So this issue has two necessary fixes:

• Ensure browsers can disconnect properly
• Ensure that the first sent message is never compressed