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
Actual behavior:
IINA crashed during termination due to the following fatal assertion in mpv:
Assertion failed: (!queue->in_process), function mp_dispatch_queue_process, file dispatch.c, line 276.
This was reported by @pleasejustgo in issue #3823 and seemed like it deserved its own issue as #3823 was triggered using Xcode sanity checks whereas this crash occurred with the production version of IINA 1.3.0.
Note that in this crash we can see that the main thread was writing to a watch later file when the crash occurred:
This is more confirmation that problems coordinating termination sometimes result in the loss of watch later settings.
See issue #3590 for an analysis of the problems seen during quit. Must confirm this issue is fixed as a part of correcting IINA to properly coordinate shutdown.
System and IINA version:
Expected behavior:
INA terminates cleanly.
Actual behavior:
IINA crashed during termination due to the following fatal assertion in mpv:
This was reported by @pleasejustgo in issue #3823 and seemed like it deserved its own issue as #3823 was triggered using Xcode sanity checks whereas this crash occurred with the production version of IINA 1.3.0.
Note that in this crash we can see that the main thread was writing to a watch later file when the crash occurred:
This is more confirmation that problems coordinating termination sometimes result in the loss of watch later settings.
See issue #3590 for an analysis of the problems seen during quit. Must confirm this issue is fixed as a part of correcting IINA to properly coordinate shutdown.
Crash report:
Steps to reproduce:
Quit IINA
menu itemUnknown, but IINA definitely needs to be fixed to properly coordinate termination.
How often does this happen?
Rarely. This is a race condition during termination.
The text was updated successfully, but these errors were encountered: