CA
Crawlee & Apify•2y ago
metropolitan-bronze

'BrowserPool: Page crashed' errors after updating packages

Hi, I recently updated these packages: 
crawlee/browser-pool v3.5.0 to v3.5.2
puppeteer v21.0.3 to v21.1.0 (and Chrome v115 to v116)
crawlee/browser-pool v3.5.0 to v3.5.2
puppeteer v21.0.3 to v21.1.0 (and Chrome v115 to v116)
It's for a simple webpage screenshot service in Nodejs running as a Docker container, that generally has about 5-10 browser contexts (incognito) open at a time. The service doesn't use a crawler, but uses the browser-pool directly. VM/container has 4GB RAM in total, of which around 750MB-1GB remains free most of the time. Never got any errors in the logs before this update, but after updating the packages it immediately starts throwing errors for any new page request, although nothing else has changed. 
ERROR BrowserPool: Page crashed.
  Error: Page crashed!
      at #onTargetCrashed (/home/pptruser/node_modules/puppeteer-core/lib/cjs/puppeteer/common/Page.js:367:28)
      at /home/pptruser/node_modules/puppeteer-core/lib/cjs/puppeteer/common/Page.js:190:45
      at /home/pptruser/node_modules/puppeteer-core/lib/cjs/third_party/mitt/index.js:1:269
      at Array.map (<anonymous>)
      at Object.emit (/home/pptruser/node_modules/puppeteer-core/lib/cjs/third_party/mitt/index.js:1:252)
      at CDPSessionImpl.emit (/home/pptruser/node_modules/puppeteer-core/lib/cjs/puppeteer/common/EventEmitter.js:88:22)
      at CDPSessionImpl._onMessage (/home/pptruser/node_modules/puppeteer-core/lib/cjs/puppeteer/common/Connection.js:449:18)
      at Connection.onMessage (/home/pptruser/node_modules/puppeteer-core/lib/cjs/puppeteer/common/Connection.js:260:25)
      at Immediate._onImmediate (/home/pptruser/node_modules/puppeteer-core/lib/cjs/puppeteer/common/NodeWebSocketTransport.js:53:36)
      at process.processImmediate (node:internal/timers:476:21)
ERROR BrowserPool: Page crashed.
  Error: Page crashed!
      at #onTargetCrashed (/home/pptruser/node_modules/puppeteer-core/lib/cjs/puppeteer/common/Page.js:367:28)
      at /home/pptruser/node_modules/puppeteer-core/lib/cjs/puppeteer/common/Page.js:190:45
      at /home/pptruser/node_modules/puppeteer-core/lib/cjs/third_party/mitt/index.js:1:269
      at Array.map (<anonymous>)
      at Object.emit (/home/pptruser/node_modules/puppeteer-core/lib/cjs/third_party/mitt/index.js:1:252)
      at CDPSessionImpl.emit (/home/pptruser/node_modules/puppeteer-core/lib/cjs/puppeteer/common/EventEmitter.js:88:22)
      at CDPSessionImpl._onMessage (/home/pptruser/node_modules/puppeteer-core/lib/cjs/puppeteer/common/Connection.js:449:18)
      at Connection.onMessage (/home/pptruser/node_modules/puppeteer-core/lib/cjs/puppeteer/common/Connection.js:260:25)
      at Immediate._onImmediate (/home/pptruser/node_modules/puppeteer-core/lib/cjs/puppeteer/common/NodeWebSocketTransport.js:53:36)
      at process.processImmediate (node:internal/timers:476:21)
Anyone else getting these errors recently, or seen them occur before? Any ideas what might be causing it, and how to resolve it? Thanks for any suggestions and help.
2 Replies
metropolitan-bronze
metropolitan-bronzeOP•2y ago
Anyone got any ideas or suggestions to address this issue?
MEE6
MEE6•2y ago
@voidmonk just advanced to level 2! Thanks for your contributions! 🎉

Did you find this page helpful?