stevenwdv
stevenwdv
I also have this issue. Here's a repro which seems to be more reliable for me: ```js import puppeteer from 'puppeteer'; import {setTimeout} from 'node:timers/promises'; const browser = await puppeteer.launch({headless:...
Should I file a Chromium bug for this?
Bug at https://crbug.com/1358933
Note: this still happens with Chromium 106.0.5249.0 from puppeteer 17.1.0
Nice, fixed in 18.1.0 as expected!
Probably related is that sometimes while closing a lot of windows Node.js exits the process because it found that some Promise could never be resolved.
@jrandolf You mean `total = 100` but now with an existing URL?
> @jrandolf You mean `total = 100` but now with an existing URL? I tried this, and the problem doesn't occur, only with an invalid URL (or e.g. https on...
FYI: still happens with puppeteer 18.0.3
Chromium update to M107 did not fix this unfortunately