Another assertion error

[Philmod]

Hey,

I'm seeing another error somtimes:

Oct 14 16:26:10 storify-webapp02 errors.log:  assert.js:102
Oct 14 16:26:10 storify-webapp02 errors.log:    throw new assert.AssertionError({
Oct 14 16:26:10 storify-webapp02 errors.log:          ^
Oct 14 16:26:10 storify-webapp02 errors.log:  AssertionError: can't remove top context
Oct 14 16:26:10 storify-webapp02 errors.log:      at Namespace.exit (/data/storify/webapp/node_modules/newrelic/node_modules/continuation-local-storage/context.js:70:12)
Oct 14 16:26:10 storify-webapp02 errors.log:      at namespace.id.process.addAsyncListener.error (/data/storify/webapp/node_modules/newrelic/node_modules/continuation-local-storage/context.js:189:58)
Oct 14 16:26:10 storify-webapp02 errors.log:      at asyncErrorHandler (/data/storify/webapp/node_modules/newrelic/node_modules/continuation-local-storage/node_modules/async-listener/glue.js:27:48)
Oct 14 16:26:10 storify-webapp02 errors.log:      at process._asyncUncaughtException (/data/storify/webapp/node_modules/newrelic/node_modules/continuation-local-storage/node_modules/async-listener/glue.js:44:12)
Oct 14 16:26:10 storify-webapp02 errors.log:      at process.EventEmitter.emit (events.js:126:20)

[othiym23]

This probably has the same underlying cause as #62, (something is trying to double-exit a namespace), and it is probably related to error-handling. Thanks for the report, and as with #62, we may want to get more information from you about your specific configuration to aid in reproducing the issue.

[othiym23]

See the resolution for #62, and keep in mind that if you're reporting these issues, it's very helpful to let me know if it's just logging an error, or if it's just spewing lots of error output to the console. Thanks!