MM5 v. 2338 simply crash after a while [#17792]

[jotixce]

Hi,
I cannot tell you why, or what I'm doing .... simply lisen to music. Now I have re-intall 2338 again, and wait. after 20 minutes doing nothing ... freezed ... went white screen ... Task Manager .... kill the process .... reinstall the v. 2326....

As I did no get a log to send you of the crash, I will like to help you by giving you something..... In one of the post you say ....

"You should locate any non sent Error logs at "%appdata%\EurekaLab s.a.s\EurekaLog\Bug Reports\" or at "%appdata%\EurekaLog\MediaMonkey" that you can attach to open ticket."

Sorry for my lack of knowledge .... where is "appdata" ???

Jordi


My PC is Intel(R) Core(TM) i5-8400 CPU @ 2.80GHz 2.81 GHz, Windows 10 Pro 20H2 installed 28/‎11/‎2020 version 19042.746

[robojock]

Just copy that line as it is " %appdata%\EurekaLab s.a.s\EurekaLog\Bug Reports\ " (without the commas) and paste it in file explorer and it will take you to that folder.

[jotixce]

There is only one folder "MediaMonkeyEngine.exe", which is empty. I have also tried the other adress you gave in the post.

Now what?

Jordi

[Lowlander]

Please capture the white screen in a debug log (step 4b) instead: https://www.mediamonkey.com/forum/viewt ... 30&t=86643 Attach it to a Support Ticket which should help the developers discover why you're seeing this.

[drakinite]

Also, you'd need a Debug build in order to get a debug log. Did you install a normal build?

[jotixce]

yes, I have install the normal. I will try the debug one.

I keep you informed.

Jordi

[jotixce]

hi,

It worked . When It have crashed after 10 minutes, I have made a print screen of the ID, but , silly of me, I copied the name of the post in the message i had to send with the log, and i lost the copy of the screen and therefor the ID number. TO be abel to track it, It has been send at European Central time 22h55.

Jordi

[Ludek]

Hi,
FYI: we have received your crash log EFEFFECD (from user Jordi) and looking into it.

Thanks!

[Ludek]

I analyzed the crash log and I see that it is crash in UPnP.dll related to checking SSDP activity (recent changes due to issue #17717)

But I am unable to identify the exact reason for the crash, I would need you to:
1) Replace you current C:\Program Files (x86)\MediaMonkey 5\UPnP.dll
by this one: https://www.dropbox.com/sh/6vszmzh3vhgi ... MNxVa?dl=0
2) Start DbgView (see item 4b here: https://www.mediamonkey.com/forum/viewt ... 30&t=86643 )
3) Start MM5 and wait 10 minutes until the crash occurs
=> submit the crash and also save output from the DbgView to a file and compress (zip/rar) and share the file with me to analyze.
e.g. send me private message with the link or attach it to eSupport ticket.

Thanks for helping us to fix the issue!

[jotixce]

Hi,

For 15 days I'm not at home, so I cannot make this for you. But as I have with me my LapTop. I will install .2338 here and see what happens.

I'll tell you what in a while ....

Jordi

[jotixce]

well ..... my findings ..... In my laptop is all OK!!!

I install the Debug .2338. Now I'm going to install the normal .2338.

ASUS laptop
AMD A6-5200 APU with Radeon(TM) HD Graphics 2.00 GHz

Window 10 Home 20H2 install 25/‎2/‎2021 comp. 19042.928

When I get back a Home, i will do the trials you mention.

Thanks

Jordi

[Peke]

HI,
Thank you for the info. At least now you can enjoy rest of these 15 days

[Ludek]

For 15 days I'm not at home, so I cannot make this for you.

ok, we have received this kind of crash from two other users today, so I contacted them via email and asked them to do the tests for me. Thanks so far and enjoy your travelling!

[jotixce]

Hi,

When I'm back home, i will aks you if you need to do the test.

Jordi

[Ludek]

I've got a log from another user and fixed the issue as: https://www.ventismedia.com/mantis/view.php?id=17792 (details in Mantis)

Until the 5.0.1.2400 is available feel free to replace your current UPnP.dll by this one https://www.dropbox.com/s/wbkvltim9i7b0tx/UPnP.dll?dl=0
=> this will prevent the crash from occuring.

BTW: The reason for subsequent crash was that SSDP has failed to bind multicast socket entirely (this is needed for UPnP/DLNA discovery).

So I guess that your network configuration is somehow specific, you are part of VPN (virtual private network) and/or you have disabled UPnP/DLNA discovery by your router ?