Skip to content

[Bug?]: Failed to open the cache entry for.. Couldn't allocate enough memory with pnpm and pnp linkers #6736

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

Open
1 task
pnispel opened this issue Mar 23, 2025 · 3 comments
Labels
bug Something isn't working

Comments

@pnispel
Copy link

pnispel commented Mar 23, 2025

Self-service

  • I'd be willing to implement a fix

Describe the bug

Switching from node-modules linker to pnpm or pnp causes this error:

➤ YN0000: ┌ Link step ➤ YN0001: │ Error: Failed to open the cache entry for @next/swc-darwin-x64@npm:14.1.4: Couldn't allocate enough memory at Zi.allocateBuffer (/Users/paulnispel/src/bb/basicblock/.yarn/releases/yarn-4.7.0.cjs:149:204603)

have tried on many version of yarn and many version of node and get the same error.

nodeLinker: pnpm
yarnPath: .yarn/releases/yarn-4.7.0.cjs

To reproduce

Large monorepo with many packages?

Environment

System:
    OS: macOS 15.3.2
    CPU: (10) arm64 Apple M1 Max
  Binaries:
    Node: 23.10.0 - /private/var/folders/r2/v37zv37558d949_l3rw575qr0000gn/T/xfs-1c10319b/node
    Yarn: 4.7.0 - /private/var/folders/r2/v37zv37558d949_l3rw575qr0000gn/T/xfs-1c10319b/yarn
    npm: 10.9.2 - ~/.nvm/versions/node/v23.10.0/bin/npm
  npmPackages:
    jest: 29.7.0 => 29.7.0

Additional context

No response

@pnispel pnispel added the bug Something isn't working label Mar 23, 2025
@MorrisonCole
Copy link

MorrisonCole commented Mar 29, 2025

I'm seeing this too with nodeLinker: node-modules in a large monorepo when upgrading from 4.2.2 -> 4.8.0 (self hosted GH runners).

Edit: doesn't occur for me on 4.7.0. Will provide more details in a separate report when I can!

@arcanis
Copy link
Member

arcanis commented Mar 29, 2025

@MorrisonCole can you run yarn set version from sources --branch 6743 (#6743) and try again?

@MorrisonCole
Copy link

Hey @arcanis - thanks for taking a look so quickly!

Can confirm that we don't see the issue with #6743 🎉

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

3 participants