Repository navigation
[Bug]: recordHar: context.close() hangs when a response's raw headers never arrive #42448
Closed as not planned
Description
Version
1.59.1; 9642f57
Steps to reproduce
npm install
npx playwright install chromium
node repro.jsExpected behavior
context.close() completes, and the HAR entry keeps the provisional headers that HarTracer._onResponse already recorded for exactly this case.
Actual behavior
context.close() never resolves.
Tearing down "context" exceeded the test timeout of 100000ms.
Additional context
reproduces when running in mcr.microsoft.com/playwright:v1.59.1-noble docker image
NOT a duplicate of #42231 as far as I can tell, but actually a different issue
Environment
System:
OS: Linux 6.10 Ubuntu 24.04.4 LTS 24.04.4 LTS (Noble Numbat)
CPU: (10) x64 VirtualApple @ 2.50GHz
Memory: 24.27 GB / 25.40 GB
Container: Yes
Binaries:
Node: 24.14.1 - /usr/bin/node
Yarn: 1.22.22 - /usr/bin/yarn
npm: 11.11.0 - /usr/bin/npm
Languages:
Bash: 5.2.21 - /usr/bin/bash
npmPackages:
playwright: ^1.59.1 => 1.59.1
Activity
fix(har): also drop pending sizes and compression barriers on flush
dgozman commentedon Aug 31, 2026
Looking at the CDP log in the repro, this is similar to #39948, which should be already fixed in v1.62.1. I'd recommend to update to the latest.
Overall, we don't really like a repro that feeds synthetic data. It might trigger some behavior in Playwright, but that does not mean it is correct in making the assumptions. We'd much prefer to see a real-life scenario to understand the actual problem before making any fixes.
dgozman commentedon Sep 4, 2026
Closing because we lack the information to act on this issue. If you update to latest and the issue persists, please file a new one with a real-world reproduction. Thank you!