You could look into streaming parsers such as Oboe.js, which specifically support the use case of parsing JSON tree's larger than the available RAM[0]. Then aga

You could look into streaming parsers such as Oboe.js, which specifically support the use case of parsing JSON tree's larger than the available RAM[0]. Then again, when you're loading such huge JSON files into a 32-bit instance of Chrome, it is likely you should look for a totally different solution to your problem. [0]: http://oboejs.com/examples#loading-json-trees-larger-than-the-available-ram http://oboejs.com/examples#loading-json-trees-larger-than-th...