Target closed error in Puppeteer: pinpointing the closed page

Direct Answer

Capture page.target().id() before the target can close. Store that ID alongside the Page reference. When a Target closed error surfaces, match it against your stored map. The error itself carries no target identifier in current Puppeteer releases.

Confirmed Behavior

• Target ID retrieval: page.target().id() returns a string ID while the target is alive. After closure the Target object detaches and id() may throw or return undefined.
• Error payload: The thrown error contains only the message Target closed with no targetId, page, or frame property.
• No reattach API: Puppeteer does not expose a method to bind an existing Page instance to a new target. Recovery requires creating a fresh page via browser.createPage() (or browser.newPage() in newer versions).

Correlation Pattern

const pageMap = new Map(); // targetId -> { page, metadata }

async function trackPage(page, metadata = {}) {
  const targetId = page.target().id();
  pageMap.set(targetId, { page, metadata, createdAt: Date.now() });
  page.on('close', () => pageMap.delete(targetId));
  return targetId;
}

try {
  await page.goto(url);
} catch (err) {
  if (err.message.includes('Target closed')) {
    for (const [tid, entry] of pageMap) {
      if (entry.page === page) {
        console.error('Target closed:', tid, entry.metadata);
        break;
      }
    }
    // Recovery: create a new page, re-navigate, re-authenticate
    const newPage = await browser.newPage();
    await trackPage(newPage, metadata);
    await newPage.goto(url);
    // re-apply cookies, auth headers, viewport, etc.
  } else {
    throw err;
  }
}

Distinguishing User Close from Crash

No flag exists on the error. You must instrument the code paths:

• Wrap deliberate page.close() calls in a helper that marks the target ID as "expected" before closing.
• Listen for browser.on('disconnected') to flag unexpected browser-level terminations.
• In the catch block, check your "expected" set. If the target ID is absent, treat it as a crash and alert accordingly.

Retry and Reattach Design Considerations

1. Idempotent actions only: Retry navigation and stateless reads. Form submissions or mutation requests need application-level idempotency keys.
2. State reconstruction: Cookies, localStorage, auth tokens, and viewport settings do not transfer. Re-apply them explicitly after creating the replacement page.
3. Backoff and limits: Exponential backoff with a max attempt count prevents tight loops during sustained browser instability.
4. Resource cleanup: Attempt page.close().catch(() => {}) on the failed page before creating a replacement to avoid target leaks.

Verification Steps

1. Run console.log(page.target().id()) immediately after page creation in your installed Puppeteer version to confirm the return type.
2. Force a closure (call page.close(), then use page) and catch the error; verify the message is exactly Target closed with no extra properties.
3. Cross-reference the caught error with your stored target ID map to confirm correlation works.

Missing Diagnostic Detail

Which Puppeteer major version are you targeting? The Target API surface and error class hierarchy shifted across major releases (for example browser.createPage() versus browser.newPage()), which affects both the catch logic and the recovery snippet above.