Alex Rudenko

@DerGernTod so you mean that this scenario works in Playwright but does not work in Puppeteer? I am curious if that means that you are testing with both libraries?

I am able to reproduce the issue (although not the error, but the exposed function is not called after restore). It looks like after the restore the wrapper set up...

@DerGernTod sorry, I am a bit confused: I do not think Playwright uses any of the Puppeteer code. I guess you mean that the error is coming from the browser...

I believe it is in v8 https://source.chromium.org/chromium/chromium/src/+/main:v8/src/inspector/v8-runtime-agent-impl.cc;l=925;drc=6251d9d96d573dcd67ca8ee6aad7bd1225a66dfa

So the error itself is as expected, but here is how it works under the hood: 1) Puppeteer registers bindings on the window of the page 2) Puppeteer installs scripts...

@Lightning00Blade FYI I am not sure about the fix here. We will be exposing the double amount of globals, it probably does not matter but I wonder if there could...

We do not document `--window-size` either and, in general, the args are up to the user to set and understand what they do. Currently, Puppeteer only supports the viewport emulation...

@kblok does it help if you also add 11 sec delay after connecting before dumping the frames?

Interesting, I wonder what the difference compared to the 'should be able to reconnect to a disconnected browser' test is. We need to create a minimal example for a website...

I think I found the cause and it is a race between creation of the page instances and targets being attached. I also noticed that pages[0] is not always returning...