Verbose flag for HTML generation

[pelikhan]

After running on some Javascript out of memory issues, I followed the nice guide on diagnosing and fixing those issues (thank you for the help). While running process-top, I could see the working set jump from 240Mb to 3.4Gb repeatidely. Is there a way to turn on some kind of uber-logging more in order to pinpoint which HTML page is generating some much memory usage. This would definitely diagnosing this further.

[KyleAMathews]

This plugin wraps Node's inspector module — if you open the generated heap file in Chrome after a build, you can see memory allocations https://www.gatsbyjs.com/plugins/gatsby-plugin-inspector/

Note: If I recall correctly, it doesn't capture activity on child processes (SSR happens in jest-worker worker processes). To get around that, it'd take some hacking but you could change the code here to not use the worker pool but instead run SSR in the parent process. That way you could see what code is doing the allocation.

Another option too is to turn off all the routes and add them back one by one to see which one is causing trouble.

[pelikhan]

Thanks!