On Thu, Mar 22, 2012 at 2:14 PM, AJ ONeal <[email protected]> wrote:
> On Mar 21, 3:36 pm, AJ ONeal <[email protected]> wrote: >> > I can see that setTimeout is actually losing events (console.log before, >> > after, and inside), but I'm still trying to reproduce it without the >> heavy >> > io load. >> >> What version of node? >> > > I saw it with 0.4 and with 0.6. > > I found a reduced case that shows a problem on 0.6.10, > but I'm not sure if it's really the same problem, but it works on my mac. > > https://gist.github.com/2163032 > > I seem to recall seeing the issue in 3 different event-heavy apps that lose events on ARM (Panda and Gumstix), but not on x86 or x64. The simplest failure was what for every file I traversed I setTimeout for 1 hour to reindex my file-based "database". However, I had forgotten to clearTimeout before the setTimeout. None of the events ever fired. Then when I tested on my mac I noticed a bajillion console.log s about indexing after an hour of running, which is when I realized the events on ARM never fired at all. AJ ONeal -- Job Board: http://jobs.nodejs.org/ Posting guidelines: https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines You received this message because you are subscribed to the Google Groups "nodejs" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/nodejs?hl=en?hl=en
