Hangs after websocket connection

[rcoup]

I have a few machines, and seem to get node-webkit-agent working against some but not others. (when I do, it's great!)

It loads the HTML then hangs with an empty grey bar at the top - if I open a Network panel the last request is the websocket. No obvious/different errors in the client.

In the log of the node process there is a difference:

... [SIGUSR2] ...
webkit-devtools-agent: Spawning websocket service process...
webkit-devtools-agent: A proxy got connected.
webkit-devtools-agent: Waiting for commands...
webkit-devtools-agent: Websockets service started on 0.0.0.0:9999

webkit-devtools-agent: new frontend connection!

Debugger.supportsSeparateScriptCompilationAndExecution is not implemented

Timeline.supportsFrameInstrumentation is not implemented
Timeline.canMonitorMainThread is not implemented
Page.canShowDebugBorders is not implemented
Page.canShowFPSCounter is not implemented
Page.canContinuouslyPaint is not implemented
Page.canOverrideGeolocation is not implemented
Page.canOverrideDeviceOrientation is not implemented

vs (working):

... [SIGUSR2] ...
webkit-devtools-agent: Spawning websocket service process...
webkit-devtools-agent: A proxy got connected.
webkit-devtools-agent: Waiting for commands...
webkit-devtools-agent: Websockets service started on 0.0.0.0:9999

webkit-devtools-agent: new frontend connection!

Timeline.supportsFrameInstrumentation is not implemented
Timeline.canMonitorMainThread is not implemented
CSS.getSupportedCSSProperties is not implemented
Network.enable is not implemented
Network.enable is not implemented
Page.getResourceTree is not implemented
CSS.enable is not implemented
Database.enable is not implemented
DOMStorage.enable is not implemented

This seems like a candidate:

Debugger.supportsSeparateScriptCompilationAndExecution is not implemented

But google isn't helping me much in tracking down when it would/wouldn't be available.

OS is Ubuntu Lucid; Node v0.8.15; nodejs, nodejs-dbg, nodejs-dev all installed on both hosts. Node versions/packages are the same. App code is the same.

Any bright ideas? Seen anything like this before?

[c4milo]

Strange, what devtools frontend version are you using?

[rcoup]

Chrome 27.0.1453.116 (OSX, but was Ubuntu Quantal last week)

[c4milo]

do you get a similar result using http://c4milo.github.io/node-webkit-agent/26.0.1410.65/inspector.html?host=localhost:9999&page=0 ?

[rcoup]

ah sorry, misread your question. Yeah, I've been using the above URL all the time to launch the session

[c4milo]

@rcoup sorry for the late response, It seems like a network problem. My guess is that some proxy in between your machine and the servers, is terminating the websockets connection.

[c4milo]

@rcoup are you using any known PaaS or straight AWS EC2, something like that?

[c4milo]

Closing for inactivity.

[aredridel]

I'm getting this too.

Straight MacOS.

[c4milo]

using http://c4milo.github.io/node-webkit-agent/26.0.1410.65/inspector.html?host=localhost:9999&page=0?

[aredridel]

Yep.