Closed Bug 1622233 Opened 3 months ago Closed 2 months ago

Crash in [@ neqo_http3::transaction_client::{{impl}}::receive]

Categories

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

Unspecified
Windows 10
defect

Tracking

()

RESOLVED FIXED
mozilla77
Tracking Status
firefox-esr68 --- unaffected
firefox74 --- unaffected
firefox75 --- disabled
firefox76 --- disabled
firefox77 --- fixed

People

(Reporter: dragana, Assigned: dragana)

References

(Blocks 1 open bug)

Details

(Keywords: crash, Whiteboard: [necko-triaged])

Crash Data

This bug is for crash report bp-339a6bff-5a38-43d9-bf6f-b301c0200310.

Top 10 frames of crashing thread:

0 xul.dll RustMozCrash mozglue/static/rust/wrappers.cpp:16
1 xul.dll mozglue_static::panic_hook mozglue/static/rust/lib.rs:89
2 xul.dll core::ops::function::Fn::call<fn src/libcore/ops/function.rs:232
3 xul.dll std::panicking::rust_panic_with_hook src/libstd/panicking.rs:475
4 xul.dll std::panicking::begin_panic<str*> src/libstd/panicking.rs:404
5 xul.dll neqo_http3::transaction_client::{{impl}}::receive third_party/rust/neqo-http3/src/transaction_client.rs:269
6 xul.dll neqo_http3::connection::Http3Connection<neqo_http3::transaction_client::TransactionClient>::handle_read_stream<neqo_http3::transaction_client::TransactionClient> third_party/rust/neqo-http3/src/connection.rs:414
7 xul.dll neqo_http3::connection_client::Http3Client::check_connection_events third_party/rust/neqo-http3/src/connection_client.rs:338
8 xul.dll neqo_http3::connection_client::Http3Client::process_http3 third_party/rust/neqo-http3/src/connection_client.rs:277
9 xul.dll mozilla::net::Http3Session::ProcessInput netwerk/protocol/http/Http3Session.cpp:212

Whiteboard: [necko-triaged]
Crash Signature: [@ neqo_http3::transaction_client::{{impl}}::receive] → [@ neqo_http3::transaction_client::{{impl}}::receive] [@ <neqo_http3::transaction_client::TransactionClient as neqo_http3::connection::Http3Transaction>::receive]

I think there's some inlining here, so this is actually in ResponseStream::receive().

Looking at that, there are two panic() statements for if ResponseStreamState is ClosePending or Closed. Could those be firing?

Flags: needinfo?(dd.mozilla)
Status: NEW → RESOLVED
Closed: 2 months ago
Flags: needinfo?(dd.mozilla)
Resolution: --- → FIXED
Assignee: nobody → dd.mozilla
Depends on: 1628459
Target Milestone: --- → mozilla77
You need to log in before you can comment on or make changes to this bug.