JS heap out of memory when using `gulp serve` about generator-teams

[StfBauer]

It has nothing to do with a leak in the ts-loader. The issue comes from NodeJS 8 where they introduced really low memory cap 1.4GB per NodeJS process. The only option to get around this limitation is to start gulp server using the following command.

gulp serve --max-old-space-size=8192

This will set the appropriate Node flag to use a max of 8Gb or whatever value you pass in.

Pre-NodeJS 8 a process could use as many memory as they want or request.

[wictorwilen]

I noticed this as well occasionally, but haven't found a good solution to it. I'll try get a closer look at it or if someone out there has some extra time over, feel free to chime in

[doxxx]

I had a quick look at it using the Chrome dev tools to connect to the gulp node process and it looks like it might be a leak in ts-loader. I saw lots of duplicate strings containing what looked like generated Javascript, and the owner stack led back to ts-loader. If I have some more time later I can try digging deeper to determine where specifically this might be happening.

[wictorwilen]

Closing this as resolved both since the build pipeline is rebuilt and the solution provided by @StfBauer above

[latonita]

I have same behavior on Node 10.15. Adding max space 8192 postpones the problem for some time.