Skip to content
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

Possible EventEmitter memory leak detected #594

Open
dbazuin opened this issue Nov 14, 2017 · 5 comments
Open

Possible EventEmitter memory leak detected #594

dbazuin opened this issue Nov 14, 2017 · 5 comments

Comments

@dbazuin
Copy link

dbazuin commented Nov 14, 2017

I get this warning when running backstop test

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

@dbazuin
Copy link
Author

dbazuin commented Nov 14, 2017

I was using BackstopJS v3.0.30 at the time.

@Kenith
Copy link
Contributor

Kenith commented Nov 15, 2017

If you are using the docket, try: --shm-size 512m, which was posted here: #537

@dbazuin
Copy link
Author

dbazuin commented Nov 15, 2017

No we are using a vragant box.

@VladimirPittner
Copy link

VladimirPittner commented Nov 16, 2017

Hi @dbazuin ,
I got this message today too.

When I was looking for what was happening with debugWindow: true, I found out it was because the browser was trying to open url undefined (I had typo in code).

So please check if your code is accessing reachable url. Probably good way to test it, is spactate with debugWindow: true. You might be getting this message if the url is unreachable.

/V

@dbazuin
Copy link
Author

dbazuin commented Nov 23, 2017

Hi Vladimir,

I will check it.

Thanks.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants