Closed ghost closed 12 years ago
Hey, thanks for taking the time to report the issue!
What version of node are you using?
I'm currently using the lastest version (0.1.30) on a vanilla install of ubuntu 9.10.
Regarding the test I did: It might take multiple runs of the example for this to happen (eg: every 3 seconds, but only after the example stops running the last time and prompt shows up). Makes me think it might be a concurrency problem with processes.
It very well might be. Unfortunately, I am unable to reproduce the issue using this version of node on OS X:
node --version
v0.1.30-3-gffb4b47
Oh, sorry, here are more details about the version:
node --version
v0.1.30-11-ge0ecf4f
Edit: I now updated node from the git repository (thinking that this might be a bug on that version), but it keeps happening. The version is now:
v0.1.30-39-g0e844d3
On another news, I'm currently running example 5 repeatedly on a new sandbox each time but on the same javascript program. The error isn't thrown even on loops as small as one second. So that strange error shouldn't affect lots of people (if any).
Are you still having this issue on a recent node version?
Unable to reproduce on any modern version. Please reopen if found to still be present on 0.4.x+
Example 5 (the Infinite loop one) sometimes throws this:
I was unable to fix it or find the reason for this.