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.

Sign up for GitHub

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

Jump to bottom

MaxListenersExceededWarning: Possible EventEmitter memory leak detected. #8

Closed
rocc-o opened this issue Jan 10, 2023 · 2 comments
Closed

MaxListenersExceededWarning: Possible EventEmitter memory leak detected. #8

rocc-o opened this issue Jan 10, 2023 · 2 comments
Labels
duplicate This issue or pull request already exists

Comments

@rocc-o
Copy link

rocc-o commented Jan 10, 2023

With Node v16.13.0 and NPM v8.1.0 on Windows 10, since critical v0.2.4 upto v1.1.0, with Eleventy v0.12.1, and now upto Eleventy v1.0.2, I'm having:

(node:20988) MaxListenersExceededWarning: Possible EventEmitter memory leak detected. 11 exit listeners added to [process]. Use emitter.setMaxListeners() to increase limit
(Use `node --trace-warnings ...` to show where the warning was created)
(node:20988) MaxListenersExceededWarning: Possible EventEmitter memory leak detected. 11 SIGTERM listeners added to [process]. Use emitter.setMaxListeners() to increase limit
(node:20988) MaxListenersExceededWarning: Possible EventEmitter memory leak detected. 11 SIGINT listeners added to [process]. Use emitter.setMaxListeners() to increase limit

Please, do you have any idea why this is happeninng? Thanks.
@rocc-o rocc-o mentioned this issue Jan 11, 2023
Open
@gregives
Copy link
Owner

Closing as this is a duplicate of #7, I'll be releasing a fix soon!

@gregives gregives added the duplicate This issue or pull request already exists label Oct 17, 2023
@gregives
Copy link
Owner

This has been fixed in v2.0.2, let me know if you have any problems with it!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
duplicate This issue or pull request already exists
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@gregives @rocc-o