Alex Rudenko

> Alternatively we could only write the prefs in Puppeteer once when the user dir doesn't have a prefs.js file yet. we could do that but then the issue would...

I think the current behavior is in that case more preferred since at least the users can provide `extraPrefsFirefox` to add extra preferences.

But at the same time, we might override the preferences in the custom profile so probably we should do what you say.

Actually, I see that for Firefox we do backup prefs.js before launching and restore them after the browser is closed. So I guess no data loss would be happening, except...

@koalex this issue is not fixed yet and it will be only possible after changes on the Firefox side. As a workaround, you can set preferences that are need in...

Hi, could you please try to create a minimal reproducible example? This error usually happens if a closed page is being interacted with (perhaps it's crashed).

The error in #onBindingCalled looks caught and the uncaught error seems to be thrown for some pending evaluate/evaluateHandle calls which might not be coming from Puppeteer internally so it would...

The dispose only dispatches an event to which puppeteer/cdp/IsolatedWorld.js:72 (waiting for execution context) rejects. I think the stacktrace might not be quite correct here since the actual place it throws...

I am able to trigger the same error with: ``` import puppeteer from "puppeteer"; const browser = await puppeteer.launch(); const page = await browser.newPage(); await page.goto('https://example.com'); async function iframes() {...

@ikreymer could you please check where the #waitForExecutionContext() that throws in https://github.com/puppeteer/puppeteer/blob/main/packages/puppeteer-core/src/cdp/IsolatedWorld.ts#L145 was called in your code? rxjs would should re-throw the error to the actual caller of #waitForExecutionContext() and...