Yep. But the stack trace appears to be almost random; here's another example:
Trace: (node) warning: Recursive process.nextTick detected. This will break in the next version of node. Please use setImmediate for recursive deferral. at maxTickWarn (node.js:377:17) at process.nextTick (node.js:480:9) at onwrite (_stream_writable.js:258:15) at WritableState.onwrite (_stream_writable.js:97:5) at Socket._write (net.js:651:5) at doWrite (_stream_writable.js:219:10) at writeOrBuffer (_stream_writable.js:209:5) at Socket.Writable.write (_stream_writable.js:180:11) at Socket.write (net.js:613:40) at Console.log (console.js:53:16) at Logger._log (/our/code/deployed/lib/logger.js:43:17) at Logger.debug (/our/code/deployed/lib/logger.js:17:10) at Sender.<anonymous> (/our/code/deployed/lib/server/sender.js:50:12) We're not subclassing event emitter in that code path. On Tuesday, 10 September 2013 00:08:00 UTC+2, Aria Stewart wrote: > > Are you subclassing EventEmitter yourself? > > > Jules <[email protected] <javascript:>> wrote: >> >> I wonder if this might be a bug in Node. >> >> The only call to process.nextTick in the stack trace is here: >> https://github.com/joyent/node/blob/v0.10.12/lib/_stream_writable.js#L258 >> >> Or perhaps we're misusing Sockets somehow. >> >> Stack trace follows: >> >> Trace: (node) warning: Recursive process.nextTick detected. This will >> break in the next version of node. Please use setImmediate for recursive >> deferral. >> at maxTickWarn (node.js:377:17) >> at process.nextTick (node.js:480:9) >> at onwrite (_stream_writable.js:258:15) >> at WritableState.onwrite (_stream_writable.js:97:5) >> at Socket._write (net.js:651:5) >> at doWrite (_stream_writable.js:219:10) >> at writeOrBuffer (_stream_writable.js:209:5) >> at Socket.Writable.write (_stream_writable.js:180:11) >> at Socket.write (net.js:613:40) >> at Raw.write (/our/code/deployed/lib/server/netsocket/raw.js:34:15) >> at Transport._doWrite >> (/our/code/deployed/lib/server/transport.js:60:16) >> at Transport.write (/our/code/deployed/lib/server/transport.js:52:7) >> at NodeTransport.write >> (/our/code/deployed/lib/server/nodetransport.js:43:28) >> Trace: (node) warning: Recursive process.nextTick detected. This will >> break in the next version of node. Please use setImmediate for recursive >> deferral. >> at maxTickWarn (node.js:377:17) >> at process.nextTick (node.js:480:9) >> at onwrite (_stream_writable.js:258:15) >> at WritableState.onwrite (_stream_writable.js:97:5) >> at Socket._write (net.js:651:5) >> at doWrite (_stream_writable.js:219:10) >> at writeOrBuffer (_stream_writable.js:209:5) >> at Socket.Writable.write (_stream_writable.js:180:11) >> at Socket.write (net.js:613:40) >> at Console.warn (console.js:61:16) >> at Console.trace (console.js:95:8) >> at maxTickWarn (node.js:377:17) >> at process.nextTick (node.js:480:9) >> at onwrite (_stream_writable.js:258:15) >> >> >>> -- -- 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 --- You received this message because you are subscribed to the Google Groups "nodejs" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
