Chrome Crash (Prod)
44ca3f2985
Automatic update from web-platform-tests Revert "Forwarding abort reason from AbortController.abort() to fetch() response" This reverts commit 9a4ed4b454753dafc8ca2c7cbbddcca222a6ed22. Reason for revert: The Suspect CL https://chromium-review.googlesource.com/q/Iea6190f533c4b87326671e0d40f7accadde0abb8 is highly likely the cause of the crash. Please see the crash report http://crash/a58c73582a6efd58. Rebase the Revert CL on top of main branch with conflicts allowed option to prevent false positive merge conflicts. If you agree with the revert CL, please approve it and mark as Commit-Queue +2 to submit it. More details can be found in the go/crash-revert-cls-creation. Original change's description: > Forwarding abort reason from AbortController.abort() to fetch() response > > Behind a flag ForwardReasonToFetchBodyAbort. > > The fetch promise itself was forwarding the abort reason. However the body methods and ReadableStream were not, as they're intended to. > > Bug: 502133195 > Change-Id: Iea6190f533c4b87326671e0d40f7accadde0abb8 > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/7759798 > Reviewed-by: Adam Rice <ricea@chromium.org> > Commit-Queue: Taylor Brandstetter <deadbeef@chromium.org> > Reviewed-by: Andreas Haas <ahaas@chromium.org> > Reviewed-by: Hiroki Nakagawa <nhiroki@chromium.org> > Cr-Commit-Position: refs/heads/main@{#1659857} > Bug: 533559790 Change-Id: Icedebf7f1fa394800d63450fda5a347398f1095d Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/8078018 Commit-Queue: Hiroki Nakagawa <nhiroki@chromium.org> Reviewed-by: Hiroki Nakagawa <nhiroki@chromium.org> Bot-Commit: rubber-stamper@appspot.gserviceaccount.com <rubber-stamper@appspot.gserviceaccount.com> Cr-Commit-Position: refs/heads/main@{#1660911} -- wpt-commits: c3b6f53850e86042ecdea3368d635c130684fa26 wpt-pr: 61243