[Bug] Possible memory leak in either workspaces foreach or version prerelease

[kasperisager]

• I'd be willing to implement a fix

Describe the bug

I seem to be experiencing a pretty consistent ENOMEM error when attempting to bump packages for prerelease in a GitHub Actions workflow:

yarn workspaces foreach --no-private --topological version --deferred prerelease

This is the latest workflow run that failed: https://github.com/Siteimprove/alfa/runs/2064158138

To reproduce

I really wish I had something more to share, but I've been unable to reproduce this locally. It seems like such a simple command that it'd be the last thing I'd expect to fail with an OOM error. I'll keep digging and share anything additional I might discover.

Environment

• OS: Ubuntu 18.04.5
• Node version: 14.16.0
• Yarn version: 2.4.0-git.20210308.hash-53e33b45

[kasperisager]

Fails under Ubuntu 20.04.2 and Node.js 15.11.0 as well: https://github.com/Siteimprove/alfa/runs/2065547455

[kasperisager]

Works under macOS 10.15 and Node.js 15.11.0: https://github.com/Siteimprove/alfa/runs/2066026535

[kasperisager]

I hit a wall on the later steps of what I was trying to achieve with this and so won't spend more time debugging it: #2585

[merceyz]

Tried to reproduce on both Windows and Ubuntu 20.4 using Node 15.11.0, 15.12.0, and 14.16.0, all of them pass

/usr/bin/time -v yarn workspaces foreach --no-private --topological version --deferred prerelease
➤ YN0000: Done in 16s 831ms
        Command being timed: "yarn workspaces foreach --no-private --topological version --deferred prerelease"
        Maximum resident set size (kbytes): 423500

[yarnbot]

Hi! 👋

This issue looks stale, and doesn't feature the reproducible label - which implies that you didn't provide a working reproduction using Sherlock. As a result, it'll be closed in a few days unless a maintainer explicitly vouches for it or you edit your first post to include a formal reproduction (you can use the playground for that).

Note that we require Sherlock reproductions for long-lived issues (rather than standalone git repositories or similar) because we're a small team. Sherlock gives us the ability to check which bugs are still affecting the master branch at any given point, and decreases the amount of code we need to run on our own machines (thus leading to faster bug resolutions). It helps us help you! 😃

If you absolutely cannot reproduce a bug on Sherlock (for example because it's a Windows-only issue), a maintainer will have to manually add the upholded label. Thanks for helping us triaging our repository! 🌟

[LaurensUP]

I'm having the same issue