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
This is rather strange that it only crashes on quic sockets on android. Regardless given that it happens on a second start, I feel that it's caused by not properly cleaning up when the process is done. Mycelium basically spawns a bunch of background tasks which run forever. Up until now, this was fine, since on desktop, if the node exits, we just exit the whole process.
On Android (and probably on iOS as well), latest
mycelium
crashed on start-stop-start cycle.steps to reproduce:
Crash message doesn't really point out to quic.
But it is fixed when we force
is_private_net
var
totrue
mycelium/mycelium/src/peer_manager.rs
Line 171 in ee34c14
Do we need QUIC on mobile device?
If no, maybe we can disable it as well.
In case we disable it, i think we still need to fix it because this crashes mean there is some process that is not gfacefully shut down
The text was updated successfully, but these errors were encountered: