Closed Bug 1819573 Opened 2 years ago Closed 2 years ago

[wpt-sync] Sync PR 38763 - Fix DCHECK in blink::BodyStreamBuffer::EndLoading

Categories

(Core :: DOM: Networking, task, P4)

task

Tracking

()

RESOLVED FIXED
112 Branch
Tracking Status
firefox112 --- fixed

People

(Reporter: wpt-sync, Unassigned)

References

(Depends on 1 open bug, )

Details

(Whiteboard: [wptsync downstream])

Sync web-platform-tests PR 38763 into mozilla-central (this bug is closed when the sync is complete).

PR: https://github.com/web-platform-tests/wpt/pull/38763
Details from upstream follow.

Adam Rice <ricea@chromium.org> wrote:

Fix DCHECK in blink::BodyStreamBuffer::EndLoading

FetchDataLoaderAsFormData::OnStateChange() would call
DidFetchDataLoadFailed() on parse failure. It then would call it again
when it finished reading the input. The double call to
DidFetchDataLoadFailed() caused a DCHECK failure in
BodyStreamBuffer::EndLoading().

Fix it by stopping reading from the input after a parse failure,
ensuring that DidFetchDataLoadFailed() is only called once.

BUG=1412007

Change-Id: I38b7815020e85cbdedc38c207c945b1dee011083
Reviewed-on: https://chromium-review.googlesource.com/4296718
WPT-Export-Revision: 1987fcddb2c412d154c9f63ddb0e71dda74636cf

Component: web-platform-tests → DOM: Networking
Product: Testing → Core

CI Results

Ran 9 Firefox configurations based on mozilla-central, and Firefox, Chrome, and Safari on GitHub CI

Total 2 tests and 1 subtests

Status Summary

Firefox

OK : 2
FAIL: 2

Chrome

OK : 2
PASS: 2

Safari

OK : 2
FAIL: 2

Links

Gecko CI (Treeherder)
GitHub PR Head
GitHub PR Base

Details

New Tests That Don't Pass

Pushed by wptsync@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/29f6e67d4853 [wpt PR 38763] - Fix DCHECK in blink::BodyStreamBuffer::EndLoading, a=testonly https://hg.mozilla.org/integration/autoland/rev/7a4b98fb3135 [wpt PR 38763] - Update wpt metadata, a=testonly
Status: NEW → RESOLVED
Closed: 2 years ago
Resolution: --- → FIXED
Target Milestone: --- → 112 Branch
You need to log in before you can comment on or make changes to this bug.