Puppeteer: Navigating frame was detached

A navigation that Puppeteer was waiting on, from page.goto(), frame.goto() or page.waitForNavigation(), could not complete because the frame being navigated was removed. Puppeteer stops waiting and rejects with this message instead of a timeout.

On the main frame this typically means the page was closed or the renderer crashed during the navigation. Heavy pages in memory-limited containers, reusing a page that another part of the script closed, or a site that closes its own window during login all lead here. On iframes it means the iframe element was removed while it was loading.

What is not wrong: the URL. The same navigation in a fresh page usually succeeds, which is why this error tends to look intermittent and is often misread as a network problem.

async function gotoWithRetry(browser, url) {
  let page = await browser.newPage();
  try {
    await page.goto(url, { waitUntil: 'domcontentloaded' });
  } catch (err) {
    if (!/frame was detached/i.test(err.message)) throw err;
    if (!page.isClosed()) await page.close();
    page = await browser.newPage();
    await page.goto(url, { waitUntil: 'domcontentloaded' });
  }
  return page;
}

Give Chrome enough shared memory and RAM, limit concurrent pages, and recycle the browser periodically in long crawls. Keep page ownership clear so only one task navigates or closes a given page, and log crash and disconnect events so intermittent failures can be correlated with memory usage.