Property 'executionContextId' of 'undefined'

[Zvih]

it seems, An error is triggered when the Cloudflare checkbox tries to be checked automatically for the second time

[mdervisaygan]

Can you add rebuild steps to the problem?

[Zvih]

@zfcsoftware Setup as I provied here #132

Run browser, go to page.

Actually, nothing special, just open page with cloudflare checkbox and got error. But checkbox is checked so error does not interfere the lib

[bookedkeeper]

Got the same error. It wasn't caught by a try/catch and crashed the script. Here's a trace:

TypeError: Cannot destructure property 'executionContextId' of 'undefined' as it is undefined.
    at <anonymous> ([...]/node_modules/puppeteer-real-browser/lib/data/puppeteer-core/src/cdp/FrameManager.ts:544:9)
    at async Promise.all (index 0)
    at FrameManager.#createIsolatedWorld ([...]/node_modules/puppeteer-real-browser/lib/data/puppeteer-core/src/cdp/FrameManager.ts:531:5)
    at async Promise.all (index 4)
    at FrameManager.initialize ([...]/node_modules/puppeteer-real-browser/lib/data/puppeteer-core/src/cdp/FrameManager.ts:210:63)
Node.js v20.16.0

Thanks for looking into this

[mdervisaygan]

@zfcsoftware Setup as I provied here #132

Run browser, go to page.

Actually, nothing special, just open page with cloudflare checkbox and got error. But checkbox is checked so error does not interfere the lib

Got the same error. It wasn't caught by a try/catch and crashed the script. Here's a trace:

TypeError: Cannot destructure property 'executionContextId' of 'undefined' as it is undefined.
    at <anonymous> ([...]/node_modules/puppeteer-real-browser/lib/data/puppeteer-core/src/cdp/FrameManager.ts:544:9)
    at async Promise.all (index 0)
    at FrameManager.#createIsolatedWorld ([...]/node_modules/puppeteer-real-browser/lib/data/puppeteer-core/src/cdp/FrameManager.ts:531:5)
    at async Promise.all (index 4)
    at FrameManager.initialize ([...]/node_modules/puppeteer-real-browser/lib/data/puppeteer-core/src/cdp/FrameManager.ts:210:63)
Node.js v20.16.0

Thanks for looking into this

Can you give me a working code that I can test? The problem you posted has already been solved. The code there does not work because it is part of somewhere. I need a code that works and gives this error.

[Zvih]

@zfcsoftware Hardly possible to trace. It usually appears after logging in to the website with a Cloudflare checkbox and after navigating to several pages. Maybe other guy can provide more info

[mdervisaygan]

I am closing the issue as it cannot be reproduced. If you find a way to reproduce it, please let me know here. Thank you.

[roockisgreat]

I have the same issue. Try this code:

const {browser, page} = await connect({
        headless: "new",
        turnstile: true,
        disableXvfb: true, 
});
await page.setRequestInterception(true);
page.on('request', request => {
      if(request.isInterceptResolutionHandled()) return;
      request.continue();
});
page.on("framenavigated", async (frame) => {
      if(frame.url().includes("cloudflare")){
          await client.send("Target.detachFromTarget", {
              targetId: frame._id,
          });
      }
});  
await page.goto("https://keepa.com/#!product/1-B0C4VQXSMT");

If i don't use setRequestInterception, the error appears after quite a few iterations. This is the only way I've found to simulate the error quickly. I use Chrome/128.0.6613.85 and Node 18.15.0.

[Zvih]

@zfcsoftware

[mdervisaygan]

I have the same issue. Try this code:

const {browser, page} = await connect({
        headless: "new",
        turnstile: true,
        disableXvfb: true, 
});
await page.setRequestInterception(true);
page.on('request', request => {
      if(request.isInterceptResolutionHandled()) return;
      request.continue();
});
page.on("framenavigated", async (frame) => {
      if(frame.url().includes("cloudflare")){
          await client.send("Target.detachFromTarget", {
              targetId: frame._id,
          });
      }
});  
await page.goto("https://keepa.com/#!product/1-B0C4VQXSMT");

If i don't use setRequestInterception, the error appears after quite a few iterations. This is the only way I've found to simulate the error quickly. I use Chrome/128.0.6613.85 and Node 18.15.0.

@zfcsoftware

The library guarantees stable operation only when used with headless false. When using 'new' it can be detected and errors can occur. When I used false, I did not encounter an error in the code.

[Zvih]

I use headless true/false and got this error sometimes

…

On Thu, Aug 29, 2024, 00:38 ZFC Software ***@***.***> wrote: I have the same issue. Try this code: const {browser, page} = await connect({ headless: "new", turnstile: true, disableXvfb: true, }); await page.setRequestInterception(true); page.on('request', request => { if(request.isInterceptResolutionHandled()) return; request.continue(); }); page.on("framenavigated", async (frame) => { if(frame.url().includes("cloudflare")){ await client.send("Target.detachFromTarget", { targetId: frame._id, }); } }); await page.goto("https://keepa.com/#!product/1-B0C4VQXSMT"); If i don't use setRequestInterception, the error appears after quite a few iterations. This is the only way I've found to simulate the error quickly. I use Chrome/128.0.6613.85 and Node 18.15.0. @zfcsoftware <https://github.com/zfcsoftware> The library guarantees stable operation only when used with headless false. When using 'new' it can be detected and errors can occur. When I used false, I did not encounter an error in the code. — Reply to this email directly, view it on GitHub <#133 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AC425UADHWXEXKMN4RXSY5DZTY7NZAVCNFSM6AAAAABM7Y6YJKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGMJWGI4TIMZRGE> . You are receiving this because you authored the thread.Message ID: ***@***.***>

[Zvih]

@zfcsoftware Hi there,
Does lib started supporting both true/false value for "headless" param ?

[mdervisaygan]

The library is not guaranteed to work except false but it does support it.

[Zvih]

@zfcsoftware Should I start a new topic about support for headless: true, or are there no plans to fix that issue?

[CarbonPool]

Re-updating the pptr patch solved my problem

[mdervisaygan]

Can you try again with the latest version?

[mdervisaygan]

#162 (comment)