Dd-trace-js: MaxListenersExceededWarning: Possible EventEmitter memory leak detected

Created on 11 Jan 2021  路  2Comments  路  Source: DataDog/dd-trace-js

Describe the bug

Getting a MaxListenersExceededWarning on tracer version 0.30.0. Would be nice to increase the listener limit to avoid warning if this expected.

DATADOG TRACER CONFIGURATION - {"date":"2021-01-11T18:04:02.062Z","os_name":"Darwin","os_version":"19.6.0","architecture":"x64","version":"0.30.0","lang":"nodejs","lang_version":"14.15.1","enabled":true,"service":"node","agent_url":{"slashes":true,"protocol":"http:","hash":"","query":"","pathname":"","auth":"","host":"127.0.0.1:8126","port":"8126","hostname":"127.0.0.1","password":"","username":"","origin":"http://127.0.0.1:8126","href":"http://127.0.0.1:8126"},"debug":false,"analytics_enabled":false,"sample_rate":1,"sampling_rules":[],"tags":{"service":"node","version":"1.0.0"},"dd_version":"1.0.0","log_injection_enabled":false,"runtime_metrics_enabled":false,"integrations_loaded":["[email protected]","http","https","fs","@hapi/[email protected]","[email protected]","net","dns","[email protected]","@elastic/[email protected]"]}
(node:89418) MaxListenersExceededWarning: Possible EventEmitter memory leak detected. 11 update listeners added to [Config]. Use emitter.setMaxListeners() to increase limit
    at _addListener (events.js:390:17)
    at Config.addListener (events.js:406:10)
    at Config.retroOn (/Users/ssingaravelu/Projects/cf-users/node_modules/dd-trace/packages/dd-trace/src/config.js:71:10)
    at new Sampler (/Users/ssingaravelu/Projects/cf-users/node_modules/dd-trace/packages/dd-trace/src/sampler.js:7:12)
    at PrioritySampler.update (/Users/ssingaravelu/Projects/cf-users/node_modules/dd-trace/packages/dd-trace/src/priority_sampler.js:69:23)
    at /Users/ssingaravelu/Projects/cf-users/node_modules/dd-trace/packages/dd-trace/src/exporters/agent/writer.js:58:31
    at /Users/ssingaravelu/Projects/cf-users/node_modules/dd-trace/packages/dd-trace/src/exporters/agent/writer.js:133:5
    at IncomingMessage.<anonymous> (/Users/ssingaravelu/Projects/cf-users/node_modules/dd-trace/packages/dd-trace/src/platform/node/request.js:40:9)
    at /Users/ssingaravelu/Projects/cf-users/node_modules/dd-trace/packages/dd-trace/src/scope/base.js:54:19
    at AsyncLocalStorage.run (async_hooks.js:295:14)
    at Scope._activate (/Users/ssingaravelu/Projects/cf-users/node_modules/dd-trace/packages/dd-trace/src/scope/async_local_storage.js:25:26)
    at Scope.activate (/Users/ssingaravelu/Projects/cf-users/node_modules/dd-trace/packages/dd-trace/src/scope/base.js:12:19)
    at IncomingMessage.bound (/Users/ssingaravelu/Projects/cf-users/node_modules/dd-trace/packages/dd-trace/src/scope/base.js:53:20)
    at IncomingMessage.emit (events.js:327:22)
    at IncomingMessage.EventEmitter.emit (domain.js:486:12)
    at endReadableNT (_stream_readable.js:1327:12)

Environment

  • Operation system: -- Unix, MacOS
  • Node version: -- 14.15.1
  • Tracer version: -- 0.30.0
  • Agent version: -- 6.22.0
bug community core

Most helpful comment

We register many listeners on the config so it's normal that it's above 10 and not a leak. The warning will be fixed in the next release.

All 2 comments

We register many listeners on the config so it's normal that it's above 10 and not a leak. The warning will be fixed in the next release.

This is fixed in the latest release.

Was this page helpful?
0 / 5 - 0 ratings