Closed
Bug 1577577
Opened 5 years ago
Closed 3 months ago
Assertion failure: self->mExpectedPushPromiseID || self->mExpectedHeaderID, at netwerk/protocol/http/Http2Session.cpp:2474
Categories
(Core :: Networking: HTTP, defect, P2)
Tracking
()
RESOLVED
INACTIVE
Tracking | Status | |
---|---|---|
firefox70 | --- | affected |
People
(Reporter: decoder, Unassigned)
References
(Blocks 1 open bug)
Details
(Keywords: assertion, testcase, Whiteboard: [necko-triaged])
Attachments
(2 files)
The attached testcase asserts on mozilla-central revision 993cf82f6bbf (build with --enable-tests --enable-address-sanitizer --disable-jemalloc --enable-optimize=-O2 --enable-fuzzing --enable-debug).
For detailed crash information, see attachment.
To reproduce the issue, perform the following steps:
- Download the attached testcase, save as "test.bin".
2a. Build with --enable-fuzzing (requires Clang and ASan, also build gtests using./mach gtest dontruntests
).
2b. Alternatively you can download builds from TC usingpython -mfuzzfetch -a --fuzzing --tests gtest
(see https://github.com/MozillaSecurity/fuzzfetch). - Run MOZ_RUN_GTEST=1 LIBFUZZER=1 FUZZER=NetworkHttp2 objdir/dist/bin/firefox test.bin
This is one of the frequent assertions that we need to fix before we can do more debug testing.
Reporter | ||
Comment 1•5 years ago
|
||
Reporter | ||
Comment 2•5 years ago
|
||
Updated•5 years ago
|
Flags: needinfo?(honzab.moz)
Comment 3•5 years ago
|
||
This one looks bad. Adding Dragana in case she can see something easily here. Otherwise, we should assess how serious this assertion is and rather handle it gracefully as a possible protocol error or ignore.
Flags: needinfo?(honzab.moz) → needinfo?(dd.mozilla)
Updated•5 years ago
|
Assignee: nobody → dd.mozilla
Status: NEW → ASSIGNED
Flags: needinfo?(dd.mozilla)
Updated•5 years ago
|
Severity: normal → S3
Priority: -- → P2
Whiteboard: [necko-triaged]
Updated•3 years ago
|
Comment 4•3 months ago
|
||
Fixed by disabling HTTP/2 push in bug 1915848.
Status: NEW → RESOLVED
Closed: 3 months ago
Resolution: --- → INACTIVE
You need to log in
before you can comment on or make changes to this bug.
Description
•