Crash WASAPI C33D26F2 : After turning on AVR (Regression MM 2024) [#22001]

[AnotherPhil]

Hi

I tried to send a log through, but the bug also causes the log code to hang, so this is the best I can do.

Steps to reproduce

1. RDC onto a PC with MM 2024 on it (any version from at least a year ago to present)
2. Disconnect the RDC session
3. Now click the play button on the MM 2024 PC. For me, it won't play and selecting File->Exit gives the following screenshot:

[AnotherPhil]

Some additional info...

I think problem manifests when the audio source changes, as the same thing often happens if I turn on my AVR (when off the AVR operates in pass-through mode direct to the TV), so connection changes as follows:

AVR Connection to TV appears as
Off PC-HDMI-TV
On PC-HDMI-AVR-HDMI-TV

Here, the issue manifests when the AVR transitions from Off to On & then back to Off again, so similar the RDCing on & off in terms of connection changes.

Do the logs get written file? If so, please send details & I will add them.

The Copy to Clipboard option only copies the "C33D26F2".

Thank-you for your consideration.

[MiPi]

Hi,
we tried with RDP and with virtual PC and cannot reproduce. It is likely problem with some specific system and drivers, as it looks like some system call is hanging and blocking correct app close.
Could you please generate debug log (see 4b) here ), zip it and attach to user ticket or send link, if larger? Thanks. Only note, you need to run DbgView before MM, to be sure it catches all debug messages, then do the repro steps. Thanks.

Michal

P.S. is it the same with out_WASAPI and out_MMDS output plugins? If so, I prefer WASAPI for debug log, it is more talkative.

[AnotherPhil]

Thank-you Michal

Ticket logged here : #16098
Re: P.S. is it the same with out_WASAPI and out_MMDS output plugins? If so, I prefer WASAPI for debug log, it is more talkative.

I don't know which output plugin is selected, but if the wrong one then I'm happy to redo, but I will need instructions on how to change.

[Lowlander]

I don't know which output plugin is selected, but if the wrong one then I'm happy to redo, but I will need instructions on how to change.

Please see: https://www.mediamonkey.com/wiki/WebHel ... ing_Output

[AnotherPhil]

Thank-you Lowlander

Checked & WASAPI was already selected, so the log file(s) should be complete.

[Peke]

Checked & WASAPI was already selected, so the log file(s) should be complete.

So if I read this correctly When you use RDC and Direct Sound all works, but When you use RDC with WASAPI MM crashes? Finally have you tried to replicate same thing without using RDC and accessing PC Directly?
I tried to replicate any way, and strangely even using RDC all worked. This all sounds like RDC hooks to PC System Audio output and it is the one that is actually making issues. Have you tried other RDC alternatives like AnyDesk, TeamViewer, UltraVNC, ... and see if any other observe same behavior.

[AnotherPhil]

Hi Peke

Thank-you for your looking into this.

>When you use RDC and Direct Sound all works
I haven't tested it yet, but that is my expectation.

>When you use RDC with WASAPI MM crashes
Yes, but it's intermittent. I don't actually use MM when I RDC on to my HTPC, but the problem manifests when I use it direct later.

>This all sounds like RDC hooks to PC System Audio output and it is the one that is actually making issues
I think the root cause is down to the audio output device changing, due to the similar issue when I turn on my AVR. Please see ticket summary for explanation:

https://www.mediamonkey.com/support/?wp ... t-id=16098

The RDC issue appears to be intermittent, so I will post the log details when it happens next. Very interesting though, switching to MediaMonkey DirectSound output appears to have resolved the issue & even continues playing the current audio track when toggling the AVR on & off. So the issue appears tied to the WSAPI driver in MM2024, as MM4 is set to WSAPI as doesn't have the problem (though the track does stop playing).

Thank-you
Phil

[Peke]

Hi,
Just update if anyone stumble to have same issue.

It is documented at https://www.ventismedia.com/mantis/view.php?id=22001 and fix will be introduced in the next Major MM release.