Open max-cura opened 11 months ago
Thanks for the bug report @max-cura, and sorry you had that happen!
Would you mind seeing if you can run through the python quick start on your system?
Also segfaults;
I ran pip3 install rerun-sdk
then ran python3 -m rerun_demo
, which gave
Rerun caught a signal: SIGSEGV
Troubleshooting Rerun: https://www.rerun.io/docs/getting-started/troubleshooting
Report bugs: https://github.com/rerun-io/rerun/issues
Rerun caught a signal: SIGSEGV
Troubleshooting Rerun: https://www.rerun.io/docs/getting-started/troubleshooting
Report bugs: https://github.com/rerun-io/rerun/issues
/opt/homebrew/lib/python3.11/site-packages/rerun_sdk/rerun_demo/__main__.py:24: DeprecationWarning: Please migrate to `rr.log(…, rr.Points2D(…))` or `rr.log(…, rr.Points3D(…))`.
See: https://www.rerun.io/docs/reference/migration-0-9 for more details.
rr.log_points("cube", positions=cube.positions, colors=cube.colors, radii=0.5)
EDIT
Again, when I ran inside LLDB, it functioned as normal:
/usr/bin/lldb $(which python3) -o 'r -m rerun_demo' -o 'c'
We tested 0.9.1 on MacOs 14.0 and 13.4 but I don't think anyone else tried 12.5.
Given that it crashes inside a setting the app icon (eframe::native::app_icon::AppTitleIconSetter::update
) it's not unlikely that this is about your older Mac version.
I know it's a big ask, but would you mind trying if the problem persists after updating your system?
Hi again @max-cura, thanks for checking with Python! Before potentially upgrading your OS, perhaps you could try out a simpler eframe based app that also uses a custom app icon like https://crates.io/crates/puffin_viewer just to confirm our suspicion?
Yeah, installed puffin_viewer and it indeed has the same pattern (segfault on start, no segfault if started in lldb). I'll try updating my system tonight.
Upgraded to macOS 14.0.
Tried to run the Rust rerun-cli
again, got this:
[2023-10-14T05:12:49Z INFO re_sdk_comms::server] Hosting a SDK server over TCP at 0.0.0.0:9876. Connect with the Rerun logging SDK.
Rerun caught a signal: SIGBUS
Troubleshooting Rerun: https://www.rerun.io/docs/getting-started/troubleshooting
Report bugs: https://github.com/rerun-io/rerun/issues
2: re_crash_handler::install_signal_handler::signal_handler
3: __platform_memmove
4: <unknown>
5: <unknown>
6: <unknown>
7: <unknown>
8: <unknown>
9: <unknown>
10: <unknown>
11: <unknown>
12: <unknown>
13: <unknown>
14: <unknown>
15: eframe::native::epi_integration::EpiIntegration::update
16: <eframe::native::run::wgpu_integration::WgpuWinitApp as eframe::native::run::WinitApp>::run_ui_and_paint
17: eframe::native::run::run_and_return::{{closure}}
18: <winit::platform_impl::platform::app_state::EventLoopHandler<T> as winit::platform_impl::platform::app_state::EventHandler>::handle_nonuser_event
19: winit::platform_impl::platform::app_state::Handler::handle_nonuser_event
20: winit::platform_impl::platform::app_state::AppState::cleared
21: std::panicking::try
22: winit::platform_impl::platform::observer::control_flow_end_handler
23: <unknown>
24: <unknown>
25: <unknown>
26: <unknown>
27: <unknown>
28: <unknown>
29: <unknown>
30: <unknown>
31: <unknown>
32: <unknown>
33: winit::platform_impl::platform::event_loop::EventLoop<T>::run_return
34: eframe::native::run::with_event_loop
35: eframe::native::run::wgpu_integration::run_wgpu
36: eframe::run_native
Rerun caught a signal: SIGBUS
Troubleshooting Rerun: https://www.rerun.io/docs/getting-started/troubleshooting
Report bugs: https://github.com/rerun-io/rerun/issues
[1] 3848 bus error rerun
Error persisted after reinstalling rerun-cli. Same as before, no error when starting from lldb.
EDIT:
puffin_viewer displayed the same symptom.
Thanks for upgrading your system and trying again. This is pretty bad indeed
The icon code is here: https://github.com/emilk/egui/blob/master/crates/eframe/src/native/app_icon.rs
Interesting that you get both a SIGSEGV and a SIGBUS
I wonder what makes @max-cura:s computer different from mine. Have you tried attaching a debugger @max-cura?
@emilk: If you read further up on the issue, max wrote that attaching the debugger removed the problem.
Describe the bug Running the example from the Rust Quick Start page segfaults on 0.9.0, 0.9.1, and 0.10.0-alpha.5. Running rerun-cli segfaults on 0.9.1, and 0.10.0-alpha.5 (rerun-cli@0.9.0 failed to build), and the current main branch (commit 432d7d2). In both cases, running the binary from inside lldb results in normal function.
To Reproduce
cargo install rerun-cli@{any of the versions given above}
and then simplyrerun
. Note that/usr/bin/lldb rerun
runs without faulting.The first example from https://www.rerun.io/docs/getting-started/rust can also be used, which will also generate a segfault.
Expected behavior No segfaults on startup.
Backtrace Stack trace
cargo install rerun-cli@0.9.1
,RUST_LOG=debug rerun
Stack trace
cargo install rerun-cli@0.10.0-alpha.5
,RUST_LOG=debug rerun
.Full output from
https://github.com/rerun-io/rerun
withcargo build -p rerun-cli
and thenRUST_LOG=debug target/debug/rerun
:Desktop (please complete the following information):
Rerun version 0.9.0, 0.9.1, 0.10.0-alpha.5, main@commit 432d7d2.