puppeteer/chromium: handle crashing memory-heavy pages?

a few ideas:

First, this may not be related to your initial problem but it will save some memory. You're opening many tabs (pages) without closing them, that can use a lot of memory if your list of Ids is long.

Try to iterate over the IDs by loading a new url instead of creating new pages.

Also you can extend the timeout to check if more time will eventually do the trick.

There are chromium flags that you can pass on when you launch puppeteer. Here is the complete Chromium switch list

You could try with: --unlimited-storage or --force-gpu-mem-available-mb.

Also this may come handy to debug: --full-memory-crash-report

You could search for all the other memory related flags there.

Here is how you can pass on the flags to puppeteer, and the other suggestions that I mentioned:

puppeteer.launch({args: ['--unlimited-storage', '--full-memory-crash-report']}).then(async browser => { const page = await browser.newPage(); for (let id of ids) { try { //const url = 'chrome://crash'; // Timeout will be 2 min and will wait till network is idle before taking the screenshot await page.goto(url + id, {timeout: 120000, waitUntil: 'networkidle0'}); await page.screenshot(); } catch (error) { console.log('Exception', id, error.message); // If you catch an error you should throw it and handle it on the parent function // or set up an event listener so you can now what's the state of your app throw new Err (error); // Since we are only opening one page and browsing from here // no need to close when you encounter an error // just goto the next iteration // page.close(); } }; browser.close(); }); 

Try passing the {args: ['--disable-dev-shm-usage']} launch option the launch() command--this is supposed to improve Puppeteer's ability to render large/complex pages.