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

[Bug?]: "Possible EventEmitter memory leak detected" when installing repository #5821

Closed
1 task
wojtekmaj opened this issue Oct 23, 2023 · 4 comments
Closed
1 task
Labels
bug Something isn't working stale Issues that didn't get attention waiting for feedback Will autoclose in a while unless more data are provided

Comments

@wojtekmaj
Copy link
Contributor

Self-service

  • I'd be willing to implement a fix

Describe the bug

Upon installing a repo (previously managed using Yarn 3) with Yarn 4, I got hit with these warnings:

➤ YN0000: · Yarn 4.0.0
➤ YN0000: ┌ Resolution step
➤ YN0000: │ MaxListenersExceededWarning: Possible EventEmitter memory leak detected. 11 close listeners added to [TLSSocket]. Use emitter.setMaxListeners() to increase limit
➤ YN0000: │ MaxListenersExceededWarning: Possible EventEmitter memory leak detected. 11 close listeners added to [TLSSocket]. Use emitter.setMaxListeners() to increase limit
➤ YN0000: │ MaxListenersExceededWarning: Possible EventEmitter memory leak detected. 11 close listeners added to [TLSSocket]. Use emitter.setMaxListeners() to increase limit
(and it goes on for 100s of lines)

To reproduce

I can't reliably reproduce that. I was under poor network conditions at a time, though, so maybe it's related?

Environment

System:
    OS: macOS 14.0
    CPU: (8) arm64 Apple M2
  Binaries:
    Node: 20.7.0 - /private/var/folders/3y/swkjq1x101b76mzjgt4pm2d80000gp/T/xfs-abf151ce/node
    Yarn: 4.0.0 - /private/var/folders/3y/swkjq1x101b76mzjgt4pm2d80000gp/T/xfs-abf151ce/yarn
    npm: 10.1.0 - /opt/homebrew/bin/npm

Additional context

No response

@wojtekmaj wojtekmaj added the bug Something isn't working label Oct 23, 2023
@indooorsman
Copy link
Contributor

+1
every time I run a clear install, this warning happens

@arcanis
Copy link
Member

arcanis commented Oct 24, 2023

Unfortunately without a reproduction it'll be very difficult to fix 🙁

@arcanis
Copy link
Member

arcanis commented Nov 16, 2023

Seems this might be a Node.js bug: nodejs/node#50136 soon to be fixed in the future 20.10 release

@arcanis arcanis added the waiting for feedback Will autoclose in a while unless more data are provided label Nov 16, 2023
@yarnbot
Copy link
Collaborator

yarnbot commented Dec 16, 2023

Hi! 👋

It seems like this issue as been marked as probably resolved, or missing important information blocking its progression. As a result, it'll be closed in a few days unless a maintainer explicitly vouches for it.

@yarnbot yarnbot added the stale Issues that didn't get attention label Dec 16, 2023
@yarnbot yarnbot closed this as not planned Won't fix, can't repro, duplicate, stale Dec 21, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working stale Issues that didn't get attention waiting for feedback Will autoclose in a while unless more data are provided
Projects
None yet
Development

No branches or pull requests

4 participants