wonderful-table-85939
09/25/2023, 3:28 PMquaint-dress-831
09/25/2023, 3:39 PMgarden
binary itself is giving out of memory messages?wonderful-table-85939
09/25/2023, 3:57 PMquaint-dress-831
09/25/2023, 4:02 PMpolite-fountain-28010
09/26/2023, 8:29 AMpkg
executable always forces the flags to be overriden even if NODE_OPTIONS='--max-old-space-size=XXX'
is set
What I'm wondering is how we even get to consume more than 4GB of memory.
Would you mind sharing some details about your garden setup so we can take a look if there's any potential memory leaks that we haven't found yet?quaint-dress-831
09/26/2023, 9:37 AMwonderful-table-85939
09/26/2023, 10:30 AMpolite-fountain-28010
09/26/2023, 1:14 PMpkg
bundler and so far I haven't seen a way to override this.
I believe command line arguments take precedence over the environment variables, so it would have to be changed in pkg
, which is a bit difficult since the project seems to no longer be a priority for vercel.
Regarding the cause of the memory leak, I've also suspected that memoization could be to blame.
Feel free to assign me as a reviewer for the PR once you open it.
I'll see if I can find a reproduction for the out of memory issue to validate any fixes there.
Could you share how large or complex your project is that triggers the OOM?@Memoize((params: ResolveProcessDependenciesParams<O>) => params.status ? params.status.state : null)
indeed fixes it.
This is amazing, thank you so much for spotting this.
I can open a PR for this right away, but I can also approve your coworkers PR if they prefer to have that contribution on record 🙂wonderful-table-85939
09/26/2023, 6:00 PMpolite-fountain-28010
09/27/2023, 9:34 AMwonderful-table-85939
09/27/2023, 1:02 PMastonishing-tomato-18259
09/27/2023, 8:37 PMwonderful-table-85939
09/27/2023, 8:40 PMastonishing-tomato-18259
09/27/2023, 8:40 PMwonderful-table-85939
10/02/2023, 6:57 PMgarden delete environment
and garden get config
die with message:
de:279114) MaxListenersExceededWarning: (node) warning: possible EventEmitter memory leak detected. 5001 listeners added. Use emitter.setMaxListeners() to increase limit.
(Use `garden --trace-warnings ...` to show where the warning was created)
(node:279114) MaxListenersExceededWarning: (node) warning: possible EventEmitter memory leak detected. 5001 listeners added. Use emitter.setMaxListeners() to increase limit.
polite-fountain-28010
10/03/2023, 1:10 PMEventEmitter
instance.
Did the process actually crash there?wonderful-table-85939
10/04/2023, 4:54 PM