Closed Bug 1656870 Opened 3 months ago Closed 3 months ago

Crash in [@ neqo_http3::recv_message::RecvMessage::receive_internal]

Categories

(Core :: Networking: HTTP, defect, P2)

Unspecified
All
defect

Tracking

()

RESOLVED FIXED
81 Branch
Tracking Status
firefox-esr68 --- unaffected
firefox-esr78 --- unaffected
firefox79 --- unaffected
firefox80 --- unaffected
firefox81 --- fixed

People

(Reporter: gsvelto, Assigned: dragana)

References

(Blocks 1 open bug)

Details

(Keywords: crash)

Crash Data

This bug is for crash report bp-ec5a2c16-0287-464d-aefc-6579b0200801.

Top 10 frames of crashing thread:

0 libxul.so RustMozCrash mozglue/static/rust/wrappers.cpp:17
1 libxul.so mozglue_static::panic_hook mozglue/static/rust/lib.rs:89
2 libxul.so core::ops::function::Fn::call src/libcore/ops/function.rs:72
3 libxul.so std::panicking::rust_panic_with_hook src/libstd/panicking.rs:474
4 libxul.so std::panicking::begin_panic src/libstd/panicking.rs:397
5 libxul.so neqo_http3::recv_message::RecvMessage::receive_internal third_party/rust/neqo-http3/src/recv_message.rs:285
6 libxul.so <neqo_http3::recv_message::RecvMessage as neqo_http3::RecvStream>::header_unblocked third_party/rust/neqo-http3/src/recv_message.rs:317
7 libxul.so neqo_http3::connection::Http3Connection::handle_read_stream 
8 libxul.so neqo_http3::connection::Http3Connection::recv_decoder 
9 libxul.so neqo_http3::connection::Http3Connection::handle_stream_readable 

This started in buildid 20200730215452. It seems like we're panicking here.

Andy, can you please look at this?

Severity: -- → S2
Flags: needinfo?(agrover)
Priority: -- → P2

This is mine. I enabled QPACK last week.

Assignee: nobody → dd.mozilla
Status: NEW → ASSIGNED
Flags: needinfo?(agrover)
Blocks: QUIC

The fix for this bug is in neqo, we need to update m.-c.

m.-c. has been update in bug 1657466. I will wait to see if the crash is fixed.

Status: ASSIGNED → RESOLVED
Closed: 3 months ago
Resolution: --- → FIXED
Depends on: 1657466
Target Milestone: --- → 81 Branch
You need to log in before you can comment on or make changes to this bug.