Issues with npm datasource updates hitting memory limits on Mend-hosted infrastructure
#40942
Replies: 13 comments 31 replies
-
|
One attempt at fixing using |
Beta Was this translation helpful? Give feedback.
-
|
#40957 is a suggested change (which we can then use on Mend-hosted) |
Beta Was this translation helpful? Give feedback.
-
|
Hi @jamietanna, we've been hitting this consistently in our repo for 4 days in a row (therefore blocking any dependency upgrades). Is there an official workaround at the moment? Happy for you to use our repo if you need a reproduction case. |
Beta Was this translation helpful? Give feedback.
-
|
A couple of tests I've done so far with (against a few repos who've reported issues): {
"toolSettings": {
"nodeMaxMemory": 1024
}
}seem to be going positively - I'll do a little bit more testing, then we'll have this set across all repos |
Beta Was this translation helpful? Give feedback.
-
|
@jamietanna As mentioned in pnpm/pnpm#8441 (comment), this situation is getting worse on pnpm v11. I wonder if Renovate could expose a way to set PNPM_MAX_WORKERS or PNPM_WORKERS (code). Reducing the number of workers might lower pnpm’s memory usage. |
Beta Was this translation helpful? Give feedback.
-
|
OK, we can now specify It'll need some rebasing of open PRs to check that it definitely does work, so would prefer not to test it without the repo owner's consent! |
Beta Was this translation helpful? Give feedback.
-
|
We're still stuck on this issue. None of the proposed solutions are working. |
Beta Was this translation helpful? Give feedback.
-
|
With the memory fix/optimization in pnpm v11.3, the situation seems to be improved. Besides, pnpm is moving to Rust implementation, the memory pressure might be further down with pnpm v12. P.S. Node v24.16.0 |
Beta Was this translation helpful? Give feedback.
-
|
Here is a reproduction: https://github.com/haines/pnpm-memory Without With With I've linked the repro on the pnpm issue: pnpm/pnpm#8441 (comment) |
Beta Was this translation helpful? Give feedback.
-
|
This was not happening to me for the past couple months, but it's now happening to me on every run after upgrading from pnpm 11.3.0 to 11.5.0. |
Beta Was this translation helpful? Give feedback.
-
|
Seems like an issue with |
Beta Was this translation helpful? Give feedback.
-
|
Setting the Context: |
Beta Was this translation helpful? Give feedback.
-
|
@jamietanna What is the status of this issue? What should we be doing? Renovate has more or less ceased working for us now, we need trigger the jobs manually and even then it only works once in a blue moon:
The comment and reproduction by haines is exactly what we are experiencing: #40942 (comment) This was happening with both pnpm 10 and 11, but it's worse in pnpm 11. We set
|
Beta Was this translation helpful? Give feedback.

Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
How are you running Renovate?
A Mend.io-hosted app
Which platform you running Renovate on?
GitHub.com
Which version of Renovate are you using?
42.95.2
Please tell us more about your question or problem
We've recently seen an increase in projects using
pnpmandyarnhitting memory issues when installing dependencies on a projectpnpmRenovate stopped working on the open-source software fast-check #40541yarnJob fails with kernel-out-of-memory #40352yarn: Frequent intermittent kernel out of memory errors (with `npm` datasource) #38880pnpm: Renovate started failing with "kernel-out-of-memory" #40940pnpm: Increase memory - job fails with kernel-out-of-memory #40935pnpm: Renovate-job started to fail with a kernel-out-of-memory Exception #40943pnpm: Renovate job fails with kernel-out-of-memory #41020pnpm: Increased resources for OSS organization gemini-hlsw #41685We're in the process of investigating this further, and will share updates in this Discussion.
Related upstream issue: pnpm/pnpm#8441
Logs (if relevant)
No response
Beta Was this translation helpful? Give feedback.
All reactions