> any possible workarounds, besides not logging the stack trace? This might fall under the "not logging the stack trace" category, but I typically only log the stack trace when there is an error. This way I only get the performance hit under infrequent circumstances, via "if (err) return callback(trace(err));" where the trace() function appends the current stack onto the error object's stack property. This happens each time the error gets passed up the callback chain, so that by the time it gets to the top-level caller it has a stack for each level of asynchronicity (see https://github.com/CSNW/async-stacktrace for more details if this approach applies to your situation).
-- peter -- Job board: http://jobs.nodejs.org/ New group rules: https://gist.github.com/othiym23/9886289#file-moderation-policy-md Old group rules: 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 unsubscribe from this group and stop receiving emails from it, send an email to nodejs+unsubscr...@googlegroups.com. To post to this group, send email to nodejs@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/nodejs/76b36030-a790-4ea5-b409-1233417b7bfc%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
