Closed Bug 1623774 Opened 1 year ago Closed 1 year ago

Crash in [@ std::io::stdio::_eprint]


(Core :: mozglue, defect)

Not set



Tracking Status
firefox76 - ---


(Reporter: mccr8, Unassigned)



(Keywords: crash, regression)

Crash Data

This bug is for crash report bp-69496e73-e772-41ae-818d-9ca350200318.

Top 10 frames of crashing thread:

0 RustMozCrash mozglue/static/rust/wrappers.cpp:17
1 mozglue_static::panic_hook mozglue/static/rust/
2 core::ops::function::Fn::call src/libcore/ops/
3 std::panicking::rust_panic_with_hook src/libstd/
4 rust_begin_unwind src/libstd/
5 std::panicking::begin_panic_fmt src/libstd/
6 std::io::stdio::_eprint src/libstd/io/
7 fluent_bundle_add_resource intl/l10n/rust/fluent-ffi/src/
8 mozilla::dom::FluentBundle_Binding::addResource dom/bindings/FluentBinding.cpp:1000
9 bool mozilla::dom::binding_detail::GenericMethod<mozilla::dom::binding_detail::NormalThisPolicy, mozilla::dom::binding_detail::ThrowExceptions> dom/bindings/BindingUtils.cpp:3205

The crash report annotations for Rust MOZ_CRASH seem to be messed up. For this report, it is 'failed printing to stderr: Broken pipe (os error 32)'. I've seen some similar ones in another language.

This doesn't seem like it is a regression, as I found a similar crash with something in 71: bp-f6c971b4-7037-4ba2-a642-34c420200316

Though it is a bit strange that there are a couple of crashes on 71, and then about 15 on 76, and nothing on versions in between.

[Tracking Requested - why for this release]: possible regression in crash report annotations for Rust crashes, which will make it more difficult to investigate any crashes we see.

See Also: → 1623778

Though it is a bit strange that there are a couple of crashes on 71, and then about 15 on 76, and nothing on versions in between.

This could be explained if there was some eprint that was in 71, then was removed in 72, and fluent added it back in 76.

It's not a problem with the annotation fortunately; what's happening is that Rust standard print functions abort on certain errors. See bug 1622732 for another example of this. The fix there was to use error!() instead but I'm not sure if that's appropriate here.

The crash has gone away from nightly as the eprintln!() statement that caused it was removed in bug 1623778. I suggest dup'ing against that bug.

Bugbug thinks this bug is a regression, but please revert this change in case of error.

Keywords: regression
Closed: 1 year ago
Resolution: --- → DUPLICATE
Duplicate of bug: 1623778
You need to log in before you can comment on or make changes to this bug.