Close browser causes Protocol error about puppeteer-stream HOT 6 OPEN

As a workaround until I find a solution you can prevent node from crashing on errors via

process.on('uncaughtException', function (err) {
  console.error(err);
});

The error is probably caused because the stream is not properly closed, I'll investigate

from puppeteer-stream.

@SamuelScheit Hey, any news on this ?

from puppeteer-stream.

I'm also seeing this same issue. Can't find a good way to close the process after the stream has finished writing.

from puppeteer-stream.

Facing same issue. @SamuelScheit Please have a look on it.

from puppeteer-stream.

The workaround that worked for me.

The most critical line is:

• await page.evaluate((index) => window.STOP_RECORDING?.(index), i); since the extension page maintains a web socket connection and recorders that try to access a closed browser.

await stream.destroy();

await new Promise((resolve) => {
  file.close(async () => {
    const pages = await browser.pages();

    for (let i = 0; i < pages.length; i++) {
      const page = pages[i];

      // @ts-expect-error - get STOP_RECORDING from extension page.
      await page.evaluate((index) => window.STOP_RECORDING?.(index), i);

      await page.close();
    }

    await browser.close();

    wss.close(() => {
      resolve(undefined);
    });
  });
});

cc. @SamuelScheit @saif-o99 @dcprime @dhavalCode @xuhpppp

from puppeteer-stream.

@SamuelScheit Thanks for your awesome library. Did you ever find a fix for this?

from puppeteer-stream.