On Wed Jan 7 17:52:01 2026 +0000, Elizabeth Figura wrote:
That's not actually what I meant, no. I mean it sounds like wmvcore is misbehaving here. Are we sure it should be sending callbacks after the IWMReader is destroyed? In fact, shouldn't it stop sending callbacks after IWMReader::Stop()? well, `WMReader_Stop` only queues the stop op, doesn't wait for it to complete. there is also no mechanism for waiting for op completion there.
and after reader is stopped there is at least one more possible status (`WMT_CLOSED`), which the callback may be invoked with. (on that thought, maybe `asf_reader_cleanup_stream` should call WMReader_Close instead of just Stop). do you suggest we add a event so we can wait for the completion of at least the close op? -- https://gitlab.winehq.org/wine/wine/-/merge_requests/9858#note_126505