The size of at least one page context chunk exceeded 500kb

[LuigiClaudio]

Hi, I'm in the process of finding what is causing one of my Gatsby V2 site builds to fail when deployed on Netlify. The site counts over 10k nodes and about 4k pages at the moment, it builds just fine on a local machine both with the gatsby-cli and the netlify-cli as well. This I guess tells me that it should all check out when deploying on Netlify but I'm hitting an error that fails the build.

10:11:58 PM: success onPreInit - 54.126s
10:11:58 PM: success initialize cache - 0.006s
10:11:59 PM: success copy gatsby files - 1.054s
10:11:59 PM: success onPreBootstrap - 0.061s
10:12:00 PM: success createSchemaCustomization - 0.009s
10:12:39 PM: success Checking for changed pages - 0.001s
10:12:39 PM: success source and transform nodes - 38.271s
10:12:43 PM: success building schema - 4.176s
10:13:47 PM: info Total nodes: 11453, SitePage nodes: 4095 (use --verbose for breakdown)
10:13:47 PM: success createPages - 63.876s
10:13:47 PM: success Checking for changed pages - 0.001s
10:13:47 PM: success createPagesStatefully - 0.109s
10:13:47 PM: success Cleaning up stale page-data - 0.149s
10:13:47 PM: success update schema - 0.014s
10:13:47 PM: success onPreExtractQueries - 0.010s
10:13:47 PM: success extract queries from components - 0.355s
10:13:47 PM: success write out redirect data - 0.001s
10:13:48 PM: success Build manifest and related icons - 0.291s
10:13:48 PM: success onPostBootstrap - 0.293s
10:13:48 PM: info bootstrap finished - 202.224s
10:13:52 PM: success run static queries - 3.804s - 2/2 0.53/s
10:13:52 PM: success write out requires - 0.056s
10:14:16 PM: success Building production JavaScript and CSS bundles - 23.927s
10:14:17 PM: warning The size of at least one page context chunk exceeded 500kb, which could lead to degraded performance. Consider putting less data in the page context.
10:14:46 PM: warning The size of at least one page context chunk exceeded 500kb, which could lead to degraded performance. Consider putting less data in the page context.
10:15:09 PM: error Command failed with exit code 1.

The error is a generic exit code 1 I believe, so I started to wonder whether any of the pages could have such a large content that it fails the build silently when deployed similar to OOM but not reported as such.

I've started to skim over the logic behind that warning message about the context chunk sizes and noticed this
https://github.com/gatsbyjs/gatsby/blob/master/packages/gatsby/src/redux/persist.ts#L98

  writeFileSync(reduxSharedFile(targetDir), v8.serialize(contents))

I'm relatively new to node and recently came across the need of replacing an implementation that was using readFileSync in favor of one that uses createReadStream in order to avoid OOM issues and that made me think about this scenario in which contents get written to the target directory. Is there any possibility that a large contents here could fail the writeFileSync method because of node running out of memory?

[LuigiClaudio]

Been looking closer to this and I've come to the conclusion that my guessing was bad. I'm keep looking into the cause of this failure, ant suggestions will be much appreciated.