Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Execution context was destroyed, most likely because of a navigation #27

Open
tonxxd opened this issue Nov 22, 2019 · 2 comments
Open

Comments

@tonxxd
Copy link

tonxxd commented Nov 22, 2019

Hello, I am getting this error when trying to record a webgl canvas in a react webpage.

Error: Execution context was destroyed, most likely because of a navigation. 
    at rewriteError (/node_modules/puppeteer/lib/ExecutionContext.js:167:15)
    at processTicksAndRejections (internal/process/task_queues.js:93:5)
    at async ExecutionContext._evaluateInternal (/node_modules/puppeteer/lib/ExecutionContext.js:120:56)
    at async ExecutionContext.evaluate (/node_modules/puppeteer/lib/ExecutionContext.js:48:12)
    at async Promise.all (index 2)
  -- ASYNC --
    at ExecutionContext.<anonymous> (/node_modules/puppeteer/lib/helper.js:111:15)
    at DOMWorld.evaluate (/node_modules/puppeteer/lib/DOMWorld.js:112:20)
    at processTicksAndRejections (internal/process/task_queues.js:93:5)
  -- ASYNC --
    at Frame.<anonymous> (/node_modules/puppeteer/lib/helper.js:111:15)
    at /node_modules/timesnap/lib/overwrite-time.js:222:18
    at Array.map (<anonymous>)
    at Object.goToTimeAndAnimate (/node_modules/timesnap/lib/overwrite-time.js:221:36)
    at /node_modules/timesnap/index.js:231:29
    at loop (/node_modules/timesnap/lib/utils.js:40:14)
    at processTicksAndRejections (internal/process/task_queues.js:93:5)

But i don't know if it could be an issue related to the wrong setup of the script, dom not loaded in time o or something else.
Can Someone please help me solve this issue?
Thanks

@tungs
Copy link
Owner

tungs commented Jan 10, 2020

Could you post what page you're trying to capture as well as what command options you're using to do it? From what I've seen, this issue can stem from using canvas capture mode on a webgl rendered canvas, though there may be other cases too.

@tungs
Copy link
Owner

tungs commented Jan 10, 2020

In the case of using canvas capture mode on a webgl rendered canvas, you can instead use the immediate canvas mode, as seen here.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants