Open bb010g opened 3 years ago
I have observed the same (modulo memory addresses) crash report as report-e4ca6a0e-32e3-43af-8f08-4158725d26b4.toml.txt
.
vayu :: ~/Downloads » diff -d report-e4ca6a0e-32e3-43af-8f08-4158725d26b4.toml.txt /tmp/report-2a5e24aa-298b-4134-b217-8fe604cbfc5b.toml
15,19c15,19
< 0: 0x55d26d50b666 - std::sys_common::backtrace::__rust_begin_short_backtrace::hf8f4b2945b22d527
< 1: 0x55d26d5467a5 - core::ops::function::FnOnce::call_once{{vtable.shim}}::hecbb3ea2547f4ebf
< 2: 0x55d26d6facca - std::sys::unix::thread::Thread::new::thread_start::h2dd53bf76d714ab0
< 3: 0x7f873bf8bead - start_thread
< 4: 0x7f873bea2d2f - __GI___clone
---
> 0: 0x56071d0e4666 - std::sys_common::backtrace::__rust_begin_short_backtrace::hf8f4b2945b22d527
> 1: 0x56071d11f7a5 - core::ops::function::FnOnce::call_once{{vtable.shim}}::hecbb3ea2547f4ebf
> 2: 0x56071d2d3cca - std::sys::unix::thread::Thread::new::thread_start::h2dd53bf76d714ab0
> 3: 0x7fae4e3a8ead - start_thread
> 4: 0x7fae4e2bfd2f - __GI___clone
I also am unsure of what caused it - I don't recall doing anything out of the ordinary prior to the crash 🤔
Describe the bug lorri just kinda crashed on me. Twice? lorri's service did not restart until the second recorded crash.
To Reproduce Steps to reproduce the behavior:
Expected behavior lorri probably didn't want to crash? Also, lorri's service should have restarted after the first crash message.
Metadata Two crash reports were generated,
/tmp/report-e4ca6a0e-32e3-43af-8f08-4158725d26b4.toml
and then/tmp/report-70d2e818-a6b2-4092-a39f-40b0bd199930.toml
.report-e4ca6a0e-32e3-43af-8f08-4158725d26b4.toml report-70d2e818-a6b2-4092-a39f-40b0bd199930.toml
Additional context