Creating videos creates memory-leak warning on the 11th test in testcafe docker image testcafe:1.20.0
See original GitHub issueWhat is your Scenario?
Running multiple tests and recording videos for each
What is the Current behavior?
the 11th test throws a MaxListenersExceededWarning
(node:19) MaxListenersExceededWarning: Possible EventEmitter memory leak detected. 11 Page.screencastFrame listeners added to [Chrome]. Use emitter.setMaxListeners() to increase limit
(Use node --trace-warnings ...
to show where the warning was created)
What is the Expected behavior?
there should be no MaxListenersExceededWarning, after any number of tests
as of docker image version 1.19.0 no warning was thrown, so something might have changed in the amount of Page.screencastFrame listener that are registered
What is your public website URL? (or attach your complete example)
https://github.com/GeorgZentgraf/testcafe-bug
What is your TestCafe test code?
see test.spec.ts
Your complete configuration file
Your complete test report
docker run test Running tests in:
- Chrome 103.0.5060.114 / Alpine Linux 3.17_alpha20220715
Getting Started
✓ 1
✓ 2
✓ 3
✓ 4
✓ 5
✓ 6
✓ 7
✓ 8
✓ 9
✓ 10
(node:19) MaxListenersExceededWarning: Possible EventEmitter memory leak detected. 11 Page.screencastFrame listeners added to [Chrome]. Use emitter.setMaxListeners() to increase limit
(Use node --trace-warnings ...
to show where the warning was created)
✓ 11
✓ 12
Screenshots
No response
Steps to Reproduce
- (install docker desktop)
- clone repo
- run
docker build . -t test
- run
docker run test
TestCafe version
docker image testcafe/testcafe:1.20.0
Node.js version
No response
Command-line arguments
default from testcafe docker image
Browser name(s) and version(s)
Chrome 103.0.5060.114
Platform(s) and version(s)
No response
Other
The warning doen’t show, when using the testcafe image version 1.19.0 Might be related to #7047
Issue Analytics
- State:
- Created a year ago
- Comments:7 (1 by maintainers)
Top GitHub Comments
Release v1.20.1-rc.2 addresses this.
Release v2.0.1-alpha.1 addresses this.