SBOX_FATAL_MEMORY_EXCEEDED error shown when Chromedriver turned 1800-1900 pages using Selenium

This error…

…implies that there is a huge memory consumption issue in Chrome that cause tabs to crash with SBOX_FATAL_MEMORY_EXCEEDED error.

Deep Dive

As per the article SBOX FATAL MEMORY EXCEEDED constantly and chrome is using large amounts of memory this issue of Chrome consuming huge memory is observed with all of the following instances:

  • Google Chrome version 80.0.3987.132 (Official Build) (64-bit)
  • Google Chrome version 82.0.4083.0 (Official Build) (64-bit)
  • Google Chrome version 82.0.4085.4 canary (64-bit)

mostly with in windows-10 systems when ESET NOD32 Antivirus is installed.

Snapshot of Chrome high memory consumption:

Snapshot of high memory usage by Chrome:

As per the article Eset consumes major memory w/ Chrome with in ESET Security Forum:

Major issue with Eset NOD AV and and Chrome: Since Chrome update to 82.0.4083 (and later 82.0.4085.4 being the latest) both on Canary and Dev channels, there’s a HUGE memory consumption issue in Chrome (>8GB) on (almost) all sites (especially gmail) that cause tabs to crash with SBOX_FATAL_MEMORY_EXCEEDED error. Removing NOD resolves the issue, reinstalling it back recreates it and so forth. There’s no such issue in Chrome Canary and Dev 82.0.4077.0.


As per the ESET support article KB3415 he most effective solution would be to enable pre-release updates in ESET Windows home products. Steps:

  • Enable pre-release updates to resolve an issue with your product.
  • Switch back to a regular update.

tl; dr

We have discussed this issue at length within the discussion ESET causing excessive renderer memory usage and the issue had been removed from the queue.

Leave a Comment