Closed Bug 1624800 Opened 5 years ago Closed 5 years ago

Crash in [@ core::option::expect_failed | <neqo_transport::crypto::CryptoStreams as core::ops::index::IndexMut<neqo_transport::tracking::PNSpace>>::index_mut]

Categories

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

Unspecified
Linux
defect

Tracking

()

RESOLVED FIXED
mozilla76
Tracking Status
firefox-esr68 --- unaffected
firefox74 --- unaffected
firefox75 --- unaffected
firefox76 --- fixed

People

(Reporter: dragana, Assigned: grover)

References

(Blocks 1 open bug)

Details

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

Crash Data

This bug is for crash report bp-af0a49dd-abed-4c94-a16b-959140200325.

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:475
4 libxul.so rust_begin_unwind src/libstd/panicking.rs:375
5 libxul.so core::panicking::panic_fmt src/libcore/panicking.rs:84
6 libxul.so core::option::expect_failed src/libcore/option.rs:1188
7 libxul.so <neqo_transport::crypto::CryptoStreams as core::ops::index::IndexMut<neqo_transport::tracking::PNSpace>>::index_mut third_party/rust/neqo-transport/src/crypto.rs:968
8 libxul.so neqo_transport::connection::Connection::handle_lost_packets 
9 libxul.so neqo_transport::connection::Connection::process_timer 

Crash Signature: [@ core::option::expect_failed | <neqo_transport::crypto::CryptoStreams as core::ops::index::IndexMut<neqo_transport::tracking::PNSpace>>::index_mut] → [@ core::option::expect_failed | <neqo_transport::crypto::CryptoStreams as core::ops::index::IndexMut<neqo_transport::tracking::PNSpace>>::index_mut] [@ core::option::expect_failed | neqo_transport::crypto::{{impl}}::index ]
Assignee: nobody → agrover

This is fixed by bug 1626799

Status: NEW → RESOLVED
Closed: 5 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla76
You need to log in before you can comment on or make changes to this bug.