webpack not freeing RAM after bundling

[meaku]

We experienced that webpack keeps the RAM it needed for bundling, even if the bundling finished. This means our server process has about 300 MB resident mem usage at the moment.

We created the bundle and spinned up the server in the same process.

Is webpack already using a separate process for the bundle process?
Is webpack holding references after bundling?

Maybe it's just the wrong setup on our side...
It would be nice to solve this problem anytime soon, because we are running out of memory ;)

[sokra]

If you have any reference to the Stats object, it will not be able to garbage collect all bundling stuff. (peerigon/alamid/blob/master/lib/core/bundle/Bundler.class.js#L25, call .toJSON() to convert it to a JSON object without references)

If you have enabled caching, it will not garbage collect the cache as long as you have a reference to the Compiler object.

webpack doesn't use a separate process.

It's not good to bundle in the same process as the server. Bundling is more a preparation step. You should separate the two steps (in production).

[meaku]

Thanks for your help :)

I tried calling toJson but it didn't work.
Although i did not find any references to the compiler in our application-logic.

Your suggestions of separate processes was on our todo-list anyway so i implemented it this way.
The bundle process was only part of the server to ease deployment during development.
We will use a separate bundle process for production anyway :)

Thanks!

[sokra]

The filesystem cache holds its content for a minute. Maybe thats the origin of the memory.