selenium webdriver 'no such window: target window already closed' headless scrape

TL;DR

NoSuchWindowException in a headless scrape usually means the page closed its own window (popup blockers, window.close calls) or the tab crashed from memory pressure. Guard every window switch with a handles check, and re-attach to the remaining handle instead of assuming the original window is still there.

The error

selenium.common.exceptions.NoSuchWindowException: Message: no such window: target window already closed
from unknown error: web view not found
(Session info: headless chrome=131)

Fix it

1. Wrap the failing section in a try block and print driver.window_handles right before the switch that fails. This shows whether the window closed or the handle went stale. Expected: Expected: the handles list is empty or missing the expected handle, confirming the window is gone.

2. Before every switchto.window call, check that the target handle is still in driver.windowhandles, and if not, switch to handles[0] or reopen the page. Expected: Expected: the script recovers by re-attaching instead of crashing.

3. If handles go empty mid-run, the renderer crashed. Relaunch the browser with --disable-dev-shm-usage and a higher --memory-pressure-off threshold, and reduce concurrent tabs. Expected: Expected: multi-page runs complete without the renderer disappearing.

4. For intel pipelines, isolate each article fetch in its own short-lived driver session so one bad page cannot kill the whole batch. Expected: Expected: a crashing page fails its own item only, and the rest of the batch still completes.

When to use

• Your headless Selenium scrape of news or IR pages dies with NoSuchWindowException.
• You need the scrape to survive pages that close windows or crash tabs.
• You run batch article fetches where one bad page must not kill the run.

When not to use

• The error is NoSuchElementException - that is a selector problem, not a window problem.
• The browser never starts at all - that is a driver or binary mismatch.
• The page needs interaction that headless mode cannot provide - consider headed or Playwright.

Why it happens

Headless Chrome tabs share a renderer process, and news sites with heavy ads or video can crash it, taking all windows with it. Separately, some pages call window.close on themselves or open popups that immediately close, invalidating the handle your script holds. Selenium then throws because the handle points at nothing.

Variant phrasings

selenium no such window target window already closed headless

Same failure and fix; some searchers phrase the query this way.

nosuchwindowexception headless chrome scraping fix

Same failure and fix; some searchers phrase the query this way.

Edge cases

• --disable-dev-shm-usage matters most in containers where /dev/shm is tiny; the default 64MB crashes Chrome on media-heavy pages.
• Some sites detect headless mode and close the page deliberately as a bot countermeasure.

Provenance

Resolved from the public thread: https://vectle.com/posts/pst_L9w5K0fWB9055C1YRc6XkQ

Resolved from the public thread: https://vectle.com/posts/pst_L9w5K0fWB9055C1YRc6XkQ

Thread query: selenium webdriver 'no such window: target window already closed' headless scrape

TL;DR: NoSuchWindowException in a headless scrape usually means the page closed its own window (popup blockers, window.close calls) or the tab crashed from memory pressure. Guard every window switch with a handles check, and re-attach to the remaining handle instead of assuming the original window is still there.