-
Notifications
You must be signed in to change notification settings - Fork 400
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Exeption #66
Comments
Thanks for the report! This was a bug that existed in older versions of the module. It's fixed in 0.12.0, which is the newest version of the module. Upgrade and open a new issue if the problem remains. |
cmcadams-newrelic
pushed a commit
to cmcadams-newrelic/node-newrelic
that referenced
this issue
Jan 29, 2024
…error-fingerprinting/vm2-3.9.17 build(deps): bump vm2 from 3.9.16 to 3.9.17 in /error-fingerprinting
jsumners-nr
pushed a commit
to jsumners-nr/node-newrelic
that referenced
this issue
Apr 11, 2024
Release/v5.0.0
jsumners-nr
pushed a commit
to jsumners-nr/node-newrelic
that referenced
this issue
Apr 16, 2024
Bumps node-test-utilities to ^4.0.0.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I am using newrelic agent
{
"name": "newrelic",
"version": "0.11.4",
"author": {
"name": "New Relic Node.js agent team",
"email": "[email protected]"
},
With NodeJS v.0.10.20
With express
Right after start I got the following exception.
(node) warning: possible EventEmitter memory leak detected. 11 listeners added. Use emitter.setMaxListeners() to increase limit.
Trace
at IncomingMessage.EventEmitter.addListener (events.js:160:15)
at IncomingMessage. (/home/ammarch/csp/analytics/countly-server/frontend/node_modules/newrelic/node_modules/continuation-local-storage/context.js:94:25)
at IncomingMessage. (/home/ammarch/csp/analytics/countly-server/frontend/node_modules/newrelic/node_modules/continuation-local-storage/context.js:94:25)
at IncomingMessage. (/home/ammarch/csp/analytics/countly-server/frontend/node_modules/newrelic/node_modules/continuation-local-storage/context.js:94:25)
at IncomingMessage. (/home/ammarch/csp/analytics/countly-server/frontend/node_modules/newrelic/node_modules/continuation-local-storage/context.js:94:25)
at IncomingMessage. (/home/ammarch/csp/analytics/countly-server/frontend/node_modules/newrelic/node_modules/continuation-local-storage/context.js:94:25)
at IncomingMessage. (/home/ammarch/csp/analytics/countly-server/frontend/node_modules/newrelic/node_modules/continuation-local-storage/context.js:94:25)
at IncomingMessage. (/home/ammarch/csp/analytics/countly-server/frontend/node_modules/newrelic/node_modules/continuation-local-storage/context.js:94:25)
at IncomingMessage. (/home/ammarch/csp/analytics/countly-server/frontend/node_modules/newrelic/node_modules/continuation-local-storage/context.js:94:25)
at IncomingMessage. (/home/ammarch/csp/analytics/countly-server/frontend/node_modules/newrelic/node_modules/continuation-local-storage/context.js:94:25)
The text was updated successfully, but these errors were encountered: