Uladzimir Havenchyk
Uladzimir Havenchyk
~~nope, @camsaul. it's not ready for review 😅~~ ready for review!
It's reimplemented in different PRs
Can reproduce on v48, 926b04a1d5
I wasn't able to find steps to reproduce the problem, it doesn't mean it's not an issue anymore
I can report the same issue with rspack, `rspack-node` process can take ~30Gb of RAM. I use `@rspack/[email protected]`, rspack config can be found [here](https://github.com/metabase/metabase/blob/master/rspack.config.js)
@h-a-n-a I'm ready to test possible fixes as just running dev server for a while increases memory consumption for me, it wasn't a problem in v1
@h-a-n-a this is what I got on `rspack serve` ``` /node_modules/@rspack/cli/node_modules/@rspack/core/dist/index.js:14665 [js] this.#instance = new instanceBinding.Rspack( [js] ^ [js] [js] Error: Missing field `enforceRelative` [js] [js] at #getInstance (/node_modules/@rspack/cli/node_modules/@rspack/core/dist/index.js:14665:22) [js]...
@h-a-n-a I used it to install canary, let me try one more time. yeah, no difference. It looks like it happens mostly when I switch branches without restarting dev server,...
downgraded rspack core and rspack cli to 1.0.1 and the issue persists, but not that significant. node process memory usage grew from 3.5Gb to 6.5Gb in an hour. with 1.1.6...
@1yasa In prev versions, memory usage was lower based on my experiments @h-a-n-a but with in memory cache disabled, every change causes full rebuild of the build