alexscheelmeyer

I am also seeing this with PhantomJS v1.8.1 on OS X and latest node-phantom. I do get an error though: ``` phantom stderr: PhantomJS has crashed. Please read the crash...

Can you specify which circumstances cause callbackOrDummy to be called with null? Generally I would think that is an error on the callers part and something that I would actually...

Only thing I can say is that I am not getting that error. You are right that it sounds like a socket.io problem. Unfortunately socket.io is crazy with the amount...

This does not work for me. Normally all PhantomJS instances exit correctly for me, but if I include this they stop exiting. Which platform are you on?

Your fix will simply ignore what is an error-condition and allow you to continue. What seems to happen is that the cmdId is unknown - meaning it is getting a...

You could try and uncomment line 73 and 82 of node-phantom.js to let it output the requests and responses. the cmdid's are in second index both for request and response....

So between those two snippets you have a "requesting 1,4,..." ? And there is two responses to that, one with cmdid 2 and one with cmdid 4? It would be...

I am able to reproduce this, seems to be weird behavior by phantomjs. It will call the callback for the first invocation of page.includeJs again on the second invocation before...

Hmm, hard to tell without an example setup where I can try to reproduce it - it could be many things I guess.

I like this. It is however a change that would break existing code so I will meditate some more on this.