"THE EMULATOR DIED" about socket.io-computer HOT 8 CLOSED

hey @CrazyMao, are you running all of the commands from the readme in order?

from socket.io-computer.

Hi, thanks a lot for replying. Yes I am, I wait a few seconds before I run each one. The first two I go ahead after they say that they're listening, the third command doesn't provide any output when I run it, it just keeps running, and the last one gives the above messages.

from socket.io-computer.

The web server works fine, I can access it with my browser, qemu runs too, I ran the command manually in terminal and it started up perfectly. It seems that the problem is in the last command. I posted another comment before but removed it since I wasn't sure that it was the source of the problem, but maybe I'll reiterate just in case it provides some insight.

In vnc.js I added a few console.log(); statements to try to narrow down where the problem was, it seems like it can't finish this loop:

for (var i = 0, o = 0; i < rect.data.length; i += 4) {
    rgb[o++] = rect.data[i + 2];
    rgb[o++] = rect.data[i + 1];
    rgb[o++] = rect.data[i];
}

After a while it just stops and I get that message in all caps, without getting the second console.log(); that's located right after. I am running this on a VM right now so maybe I don't have enough memory? Though at home I tried it on my Ubuntu partition and was getting the same message, although I didn't try to debug it like this.

from socket.io-computer.

@CrazyMao hmm yeah it could be a memory issue, but I'm really not sure. I experienced a similar problem a while ago, but I thought it had been fixed by only painting the diffs between frames.

Are all of the default ports okay for you to use?

Also, you can get a more specific error message by running emu.js directly rather than using the forever-wrapper that emuRunner provides. Try that and let me know what the error is, if you can.
If you are able to debug it any more let me know and I could try to help!!

from socket.io-computer.

I've been trying older versions of the repo to see if I could get anything to work, commit 6a74a7944562c291fdb560fc5c4d9bd0e1b36f6b works well, pretty slow but it works; at least this proves that the ports are okay.

I tried running emu.js by itself like you suggested and it produced a seg fault (to my surprise, I increased the VM memory to 4GB). I don't have much experience using core dumps to debug the problem, I can send it over if you want to take a look, let me know. I learned about the node-inspector debugger so I'll try playing around with that and let you know if I find anything more specific. I appreciate your help!

from socket.io-computer.

So, interestingly enough, when I run emu.js through node-inspector in debug node, it works just fine. The only thing that comes to mind at this point is the speed of execution, I just do Step over next function call over and over until it starts, and then it works. Regular execution still seg faults.

from socket.io-computer.

So I tried it on another computer with 16GB of RAM and it works fine, curious why it needs so much though. Anyways for all intents and purposes it works, thanks for your help.

from socket.io-computer.

@CrazyMao, weird, but I'm glad you were able to get something working. In the future it would be sweet to try to reduce memory requirements, because that seems unreasonably large.

from socket.io-computer.