Crash on macos (m1) #93
Assignees
Labels
Comments
|
In the current master branch (5edffbe), try running a debug build from a terminal with If I'm reading your log properly, it looks like |
|
Hmm, after staring at the By the way, thanks for the bug report! I'm happy to hear that you're getting some use out of this software. You know, you might be the first person ever to run this on an M1 processor? |
|
Ok just tried it out, still have a crash, but i do have more logging. I looked at the line of code that the backtrace reported, but i didn't have any added wisdom to fix. |
|
Ooops, i forgot to add the |
|
Ok .... i got it to run, but only in the debugger, but hey, that's progress. I looked at the function in the log above eitherway, it runs under the debugger, but still crashes running it normally. here's the log when running it normally. |
For me, fn fuse(self) -> Fuse<Self>
where
Self: Sized,
{
assert_stream::<Self::Item, _>(Fuse::new(self))
}
I'm not sure why you're getting no backtrace with your |
|
I just did some looking around. I believe that this might be a bug in buttplug. This change by-passes warp and iced and still crashes. buttplug::start_server(application_state_db.clone(), initial_config_loaded_tx, application_status_sender).await;
+ std::thread::sleep(std::time::Duration::from_secs(3)); // added sleep
+ std::process::exit(0); // never executes this line, crashes before. Do you know if anyone else has run this on a Mac? I wonder if its an issue related to their permission system. |
Well dang, if it's crashing without warp or iced, that rules most things out. What's left? Buttplug itself obviously, and I guess Tokio? I wonder if this is the Tokio runtime getting into some weird bad state and causing crashes at unexpected times in unexpected places. I've got zero ideas, and I don't have any M1 hardware I can try to reproduce on.
No idea. I have zero telemetry and for some reason people tend to be a bit private about their use of this software. But given that this is mostly used by Neos folks and Neos has essentially zero Mac support, I'd be very surprised if you aren't the first Mac user, M1 or otherwise. |
Yeah, i'll dig in a little more. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
Crash on startup.
To Reproduce
cargo runwill crash.Additional context
Trying to debugging this to no avail. This is kind of head-scratcher. Let me know if there's something you want me to try or code to write.
Older versions (for example git ref
5d9485885f0a6bb0e0a6c710e99e2937f3af0dcc) will run insidelldb, butcargo runandtarget/debug/buttplug-litewill always crash.Currently, checkout from
masterandcargo runwill crash and running it insidelldbwill crash. I've been trying to figure it out on my own, but figured i submit a bug in case its something you had seen before.Running in side
lldbThe text was updated successfully, but these errors were encountered: