Version
1.52.0
Steps to reproduce
- Clone https://github.com/sapphi-red-repros/playwright-wait-response-against-worker-protocol-error
- Run
npm i
- Run
node index.js
- Errors at
const response = await (await reqPromise).text()
Expected behavior
No error happens and response console.log("Hello from Worker") is output.
Actual behavior
The following error happens:
response.text: Protocol error (Network.getResponseBody): No resource with given identifier found
Additional context
This works with 1.50.1 and does not work with 1.51.0.
I encountered a bug in Chromium 134.0.6998.35 that could be related (this one was fixed by 134.0.6998.89).
https://issues.chromium.org/issues/401927511
Since 1.51.0 and 1.51.1 uses Chromium 134.0.6998.35, I thought it was caused by the same root cause. But given that 1.52.0 uses Chromium 136.0.7103.25, it seems it's a separate bug.
Environment
System:
OS: Windows 11 10.0.22631
CPU: (24) x64 AMD Ryzen 9 5900X 12-Core Processor
Memory: 15.18 GB / 31.92 GB
Binaries:
Node: 22.14.0 - C:\Program Files\nodejs\node.EXE
Yarn: 1.22.22 - C:\Program Files\nodejs\yarn.CMD
npm: 10.9.2 - C:\Program Files\nodejs\npm.CMD
pnpm: 10.8.1 - C:\Program Files\nodejs\pnpm.CMD
bun: 1.2.3 - ~\AppData\Local\Microsoft\WinGet\Links\bun.EXE
IDEs:
VSCode: 1.99.3 - C:\Users\green\AppData\Local\Programs\Microsoft VS Code\bin\code.CMD
Languages:
Bash: 5.1.16 - C:\Windows\system32\bash.EXE
npmPackages:
playwright: 1.52.0 => 1.52.0
Version
1.52.0
Steps to reproduce
npm inode index.jsconst response = await (await reqPromise).text()Expected behavior
No error happens and
response console.log("Hello from Worker")is output.Actual behavior
The following error happens:
Additional context
This works with 1.50.1 and does not work with 1.51.0.
I encountered a bug in Chromium 134.0.6998.35 that could be related (this one was fixed by 134.0.6998.89).
https://issues.chromium.org/issues/401927511
Since 1.51.0 and 1.51.1 uses Chromium 134.0.6998.35, I thought it was caused by the same root cause. But given that 1.52.0 uses Chromium 136.0.7103.25, it seems it's a separate bug.
Environment
System: OS: Windows 11 10.0.22631 CPU: (24) x64 AMD Ryzen 9 5900X 12-Core Processor Memory: 15.18 GB / 31.92 GB Binaries: Node: 22.14.0 - C:\Program Files\nodejs\node.EXE Yarn: 1.22.22 - C:\Program Files\nodejs\yarn.CMD npm: 10.9.2 - C:\Program Files\nodejs\npm.CMD pnpm: 10.8.1 - C:\Program Files\nodejs\pnpm.CMD bun: 1.2.3 - ~\AppData\Local\Microsoft\WinGet\Links\bun.EXE IDEs: VSCode: 1.99.3 - C:\Users\green\AppData\Local\Programs\Microsoft VS Code\bin\code.CMD Languages: Bash: 5.1.16 - C:\Windows\system32\bash.EXE npmPackages: playwright: 1.52.0 => 1.52.0