Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

We either navigate top level or have old version of the navigated frame

See original GitHub issue

I’m trying to get core-js usage statistics in the wild and check the top 10000 sites by puppeteer (1 browser, pages by the number of CPUs), script. In most cases, after some thousands of checked sites, I have this error and I can’t catch it. Looks like an equal of #3309.

/***/core-js/node_modules/puppeteer/lib/cjs/puppeteer/common/assert.js:26
        throw new Error(message);
              ^

Error: We either navigate top level or have old version of the navigated frame
    at Object.assert (/***/core-js/node_modules/puppeteer/lib/cjs/puppeteer/common/assert.js:26:15)
    at FrameManager._onFrameNavigated (/***/core-js/node_modules/puppeteer/lib/cjs/puppeteer/common/FrameManager.js:196:21)
    at /***/core-js/node_modules/puppeteer/lib/cjs/puppeteer/common/FrameManager.js:57:64
    at /***/core-js/node_modules/puppeteer/lib/cjs/vendor/mitt/src/index.js:51:62
    at Array.map (<anonymous>)
    at Object.emit (/***/core-js/node_modules/puppeteer/lib/cjs/vendor/mitt/src/index.js:51:43)
    at CDPSession.emit (/***/core-js/node_modules/puppeteer/lib/cjs/puppeteer/common/EventEmitter.js:72:22)
    at CDPSession._onMessage (/***/core-js/node_modules/puppeteer/lib/cjs/puppeteer/common/Connection.js:225:18)
    at Connection._onMessage (/***/core-js/node_modules/puppeteer/lib/cjs/puppeteer/common/Connection.js:101:25)
    at WebSocket.<anonymous> (/***/core-js/node_modules/puppeteer/lib/cjs/puppeteer/node/NodeWebSocketTransport.js:13:32)

Steps to reproduce

Tell us about your environment:

Puppeteer version: 8.0.0
Platform / OS version: M1, MacOS 11.2.3
Node.js version: 15.12

What steps will reproduce the problem?

Copy script by the link above
Install dependencies
Run with param -l=10000

Issue Analytics

State:
Created 2 years ago
Reactions:8
Comments:17 (1 by maintainers)

Top GitHub Comments

3reactions

Pashtedcommented, May 23, 2022

Anyone has solution for this?

you can try the solution, described there https://github.com/apify/apify-js/pull/1348 (launch with --disable-site-isolation-trials arg) it fixed the same issue for me

but browsing may become less secure. google it.

0reactions

VedantGonnadecommented, Aug 4, 2022

In my case, the error was resolved by using “load” and providing a timeout of 3 seconds: await page.goto(<url>, { waitUntil: ["load", "domcontentloaded", "networkidle2"], timeout: 120000 }); await page.waitForTimeout(3000);

Top Results From Across the Web

Erratic but frequent error on puppeteer: "We either navigate ...

Erratic but frequent error on puppeteer: "We either navigate top level or have old version of the navigated frame".

How to use the pyppeteer.errors.PageError function in ...

get ('id', '')) if not (isMainFrame or frame): raise PageError('We either navigate top level or have old version ' 'of the navigated frame')...

Use PuppeteerSharp.Frame.Navigated in Puppeteer-sharp ...

Learn how to use Navigated method in PuppeteerSharp.Frame for your next Puppeteer-sharp project with LambdaTest Automation Testing Advisor.

Unable to click on the CONFIGURATION link - xk6-browser

... we either navigate top level or have old version of the navigated frame----------] 1 VUs 00m08.9s/10m0s 0/1 iters, 1 per VU goroutine ......

Source code for pyppeteer.frame_manager - GitHub Pages

_onFrameNavigated (event.get('frame'))) client.on('Page. ... or frame): raise PageError('We either navigate top level or have old version ' 'of the navigated ...