Closed Bug 1701983 Opened 3 years ago Closed 1 year ago

Crash in [@ osclientcerts_static::manager::Manager::maybe_find_new_objects]

Categories

(Core :: Security: PSM, defect)

Unspecified
macOS
defect

Tracking

()

RESOLVED WORKSFORME

People

(Reporter: aryx, Unassigned)

References

(Blocks 1 open bug)

Details

(Keywords: crash)

Crash Data

9 crashes on 6+ machines, 7/9 during the last week on central and beta

Crash report: https://crash-stats.mozilla.org/report/index/f9dc79b4-96fb-4b50-8559-e81fb0210327

Reason: EXC_SOFTWARE / SIGABRT

Top 10 frames of crashing thread:

0 libsystem_kernel.dylib __pthread_kill 
1 libsystem_c.dylib abort 
2 libosclientcerts.dylib panic_abort::__rust_start_panic::abort library/panic_abort/src/lib.rs:37
3 libosclientcerts.dylib __rust_start_panic library/panic_abort/src/lib.rs:32
4 libosclientcerts.dylib rust_panic library/std/src/panicking.rs:640
5 libosclientcerts.dylib std::panicking::rust_panic_with_hook library/std/src/panicking.rs:610
6 libosclientcerts.dylib std::panicking::begin_panic_handler::{{closure}} library/std/src/panicking.rs:497
7 libosclientcerts.dylib std::sys_common::backtrace::__rust_end_short_backtrace library/std/src/sys_common/backtrace.rs:141
8 libosclientcerts.dylib rust_begin_unwind library/std/src/panicking.rs:493
9 libosclientcerts.dylib std::panicking::begin_panic_fmt library/std/src/panicking.rs:435

I'm pretty sure this is due to an underlying issue with the logging library. Logging isn't enabled by default, so I'm not concerned about this in release audiences.

Severity: -- → S4

Closing because no crashes reported for 12 weeks.

Status: NEW → RESOLVED
Closed: 1 year ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.