Puppeteer: Execution context was destroyed, most likely because of a navigation

Puppeteer runs your page.evaluate(), page.$eval(), page.$$eval() and element-handle methods inside the JavaScript execution context of the current document. When the page navigates or reloads, Chrome destroys that context and creates a new one. Any call still running in, or bound to, the old context fails with this message, because the code and objects it relied on no longer exist.

It nearly always means two things happened at once: your script was evaluating or reading the DOM while the page was leaving. Typical triggers are a click that submits a form followed immediately by an evaluate, a site that redirects shortly after load, or a loop that clicks a link on each iteration and then reads data before the new page has arrived.

What is not wrong: the evaluated function itself. Run it again once the new document is loaded and it usually succeeds.

// Collect URLs first, then visit them; no stale contexts
const links = await page.$$eval('a.product', as => as.map(a => a.href));
for (const url of links) {
  await page.goto(url, { waitUntil: 'domcontentloaded' });
  const title = await page.$eval('h1', el => el.textContent.trim());
  console.log(title);
}

Treat every action that can navigate as a point where all handles become invalid. Extract plain values (strings, numbers) from the page rather than carrying handles across steps, and pair navigation triggers with an explicit wait for the destination. Locator-based actions re-query the page and are less exposed to this race.