You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Based on the information you have shared, it seems most likely that this is not a Tokio bug. This error can happen if, for example, you use unsafe code to run the destructor of the UnboundedSender and then attempt to use it afterwards.
Version:
`cargo tree | grep tokio`
Platform
macOS 15.2.0 (24C101)
Description
EXC_BAD_ACCESS
error onUnboundedSender::send
.Stacktrace
The type that is sent through the channel is here: https://github.com/firezone/firezone/blob/macos-client-1.4.0/rust/connlib/clients/shared/src/eventloop.rs#L29-L36
That is unfortunately all the info I have. This stacktrace came from a crash report from one of our users. It also only happened once.
The text was updated successfully, but these errors were encountered: