Repository navigation
fix(network): reject body reads after document disposal - #43574
Devin Rousso (dcrousso) wants to merge 1 commit into
Conversation
`RenderDocument` can discard a document without reporting request completion track body availability separately and reject pending reads when their document is discarded leave actual network completion unchanged so keepalive requests can continue Fixes: <#43508>
Test results for "tests 1"23556 passed, 701 skipped Merge workflow run. |
Test results for "MCP"1 failed 5188 passed, 614 skipped Merge workflow run. |
|
Hi, I'm the Playwright bot and I took a first look at the CI failure. 🟢 The failure is a confirmed pre-existing flake
DetailsPre-existing flake
Triaged by the Playwright bot - agent run |
Dmitry Gozman (dgozman)
left a comment
There was a problem hiding this comment.
I think we should figure out why it hangs. I would assume that asking for a response body will reject once the render process is dead. If that does not happen, something seems wrong.
|
this is related to the
we could also disable |
|
I'll look into fixing this in Chromium. |
Chromium can discard a document without reporting request completion, leaving body reads pending
track body availability separately and reject reads when their document is discarded without completing keepalive requests
fixes #43508