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
Somehow something major changed in how the app is compiled on OSX. Somehow it always crashes when the onTimerEnd() callback is called for an interval.
I already had a deeper look into this. I am not quite why it happens, but the issue seems to be caused by a weird interaction of three things:
running the server as a daemon
running the server code inside a tokio runtime
making OS-calls (e.g. for sound playback or notification display)
None of these three things seems to cause issues on its own - they all seem to work fine, as soon as I leave one of the three out of the equation. (so no daemon -> tokio + sound works fine, no tokio -> daemon + sound works fine, no sound/notification -> no crash)
Maybe there is something inherently wrong with the way my server is structured. I will have to take a deeper look into server-side tokio code and how it handles blocking and threads.
The text was updated successfully, but these errors were encountered:
Somehow something major changed in how the app is compiled on OSX. Somehow it always crashes when the
onTimerEnd()
callback is called for an interval.I already had a deeper look into this. I am not quite why it happens, but the issue seems to be caused by a weird interaction of three things:
None of these three things seems to cause issues on its own - they all seem to work fine, as soon as I leave one of the three out of the equation. (so no daemon -> tokio + sound works fine, no tokio -> daemon + sound works fine, no sound/notification -> no crash)
Maybe there is something inherently wrong with the way my server is structured. I will have to take a deeper look into server-side tokio code and how it handles blocking and threads.
The text was updated successfully, but these errors were encountered: