1

I read this: is node.js' console.log asynchronous? which says that stdout used to be asynchronous. However, I'm still seeing this problem in some specific cases like this:

console.log("first");
console.log("second");
throw "bah";

I had a lot of difficulty boiling down my application into this example. The issue here is that "first" prints, but "second" does not. Wth? Has anyone seen this type of problem before?

The version of node i'm using is: node-v0.10.3-x64

Community
  • 1
  • 1
B T
  • 57,525
  • 34
  • 189
  • 207
  • They both print out for me on v0.10.0-x64. Weird though. Maybe stdout isn't being fully flushed beforehand? What if you just throw an exception yourself? – loganfsmyth Apr 11 '13 at 02:07
  • Pure exception exhibits the problem too - edited the question to make that clearer – B T Apr 11 '13 at 02:15

1 Answers1

0

Looks like this is a bug in node.js specific to windows. This is the likely bug:

https://github.com/joyent/node/issues/3584

B T
  • 57,525
  • 34
  • 189
  • 207