OOM after upgrade from 4.25 to 5.11 #38357
Labels
status: triage needed
Issue or pull request that need to be triaged and assigned to a reviewer
type: bug
An issue or pull request relating to a bug in Gatsby
Preliminary Checks
Description
This is a followup to #25858 with hopes that we can get to the bottom of the memory problems with new Gatsby versions.
While I don't know whether I'll be able to provide minimal repro, I do have a repository that:
gatsby develop
flags: { DEV_SSR: true }
Since he requested as much before closing the previous issue, I will mention @pvdz
I'm fully aware that not providing a minimal repro is not an ideal start, but it seems to me that getting that amounts to practically getting the solution… I am open to suggestions & requests for further debug information that would point you to a place of the memory leak... I'd say that even some more interactive debug session might not be out of question (at least timing-wise) if the desire would be there and if Peter is indeed still in Netherlands (Prague here)
Reproduction Link
…
Steps to Reproduce
...
Expected Result
Finishing builds regardless of used mode
Actual Result
build
develop without
dev_ssr
develop with
dev_ssr
Killed after some time by system OOM killer.
There is one process that stands out by consuming outrages amounts of memory with command-line attribute reported as
.cache/tmp-xxx
(by thesystem-monitor
Ubuntu utility)Environment
Config Flags
No response
The text was updated successfully, but these errors were encountered: