Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

[test-runner] MaxListenersExceededWarning

See original GitHub issue

The most recent version logs me a:

(node:30487) MaxListenersExceededWarning: Possible EventEmitter memory leak detected. 11 Debugger.paused listeners added. Use emitter.setMaxListeners() to increase limit

I wasn’t getting this in 0.6.46, but in 0.6.50 I do.

Not sure if they are related by anything but coincidence, but after that I get some:

Error while collecting browser logs: Evaluation failed: window.__wtr_browser_logs__ is undefined

Logs that I didn’t get before, though not on all tests, which would seem more expected here.

Issue Analytics

State:
Created 3 years ago
Reactions:1
Comments:14 (14 by maintainers)

Top GitHub Comments

1reaction

LarsDenBakkercommented, Jul 31, 2020

Tracking issue https://github.com/microsoft/playwright/issues/3250

1reaction

LarsDenBakkercommented, Jul 31, 2020

@Niznikr thanks for the info, it helps a lot. I think that’s probably related to https://github.com/modernweb-dev/web/issues/238

I fixed window.__wtr_browser_logs__ is undefined, I found out that native warnings thrown by the browser itself don’t have access to this script on the window. Not sure if it’s related to timing, or just a different execution context.

I found out that MaxListenersExceededWarning is a memory leak in playwright itself, I’ll file an issue and maybe a PR on their side.

Top Results From Across the Web

MaxListenersExceededWarning: Possible EventEmitter ...

MaxListenersExceededWarning : Possible EventEmitter memory leak detected #3877 ... WebdriverIO version: 5.7.14; Mode: WDIO Testrunner ...

How do I troubleshoot MaxListenersExceededWarning ...

I've tried specifying the --trace-warnings command-line argument, but it doesn't seem to do anything. Specifically, I modified my test runner ...

Possible EventEmitter memory leak detected - Code Help ...

I am in need of urgent help. (node:630) MaxListenersExceededWarning: Possible EventEmitter memory leak detected. 11 message listeners added to [Client].

Process | Node.js v19.3.0 Documentation

'MaxListenersExceededWarning' - Indicates that too many listeners for a given event have been registered on either an EventEmitter or EventTarget .

cypress-io/cypress - Gitter

... MaxListenersExceededWarning: Possible EventEmitter memory leak detected. ... The Cypress test runner is not loading - I have tried to run the Script ......