Page 3 of 3

Re: MediaMonkey v4.1.21.1867 Access Violation [#14897]

Posted: Thu Jun 28, 2018 2:26 pm
by ZvezdanD
As I explained in Mantis, the main reason why I keep only exe files from different builds is because of saving space and it worked fine in that way until some point in time.

Here are my new tests:
MediaMonkey-1751 - the latest build that works without UPnP.dll
MediaMonkey-1764 - reset virtual machine without UPnP.dll
MediaMonkey-1778 - reset virtual machine without UPnP.dll
MediaMonkey-1783 - reset virtual machine without UPnP.dll
MediaMonkey-1801 - reset virtual machine without UPnP.dll
MediaMonkey-1836 - unresponsive without UPnP.dll
MediaMonkey-1866 - unresponsive without UPnP.dll
MediaMonkey-1867 - unresponsive without UPnP.dll
MediaMonkey-1868 - unresponsive without UPnP.dll

Re: MediaMonkey v4.1.21.1867 Access Violation [#14897]

Posted: Fri Jun 29, 2018 4:18 am
by Ludek
I can't replicate, for me the latest build works without UPnP.dll, another possibility is to disable media sharing, menu Options > Media Sharing and disable the server. This should prevent the "uncompatible message" from appearing.

Re: MediaMonkey v4.1.21.1867 Access Violation [#14897]

Posted: Fri Jun 29, 2018 5:16 am
by ZvezdanD
If you read the Issue in Mantis that I mentioned a few posts ago, you will see that I already have Media Sharing disabled. I wouldn't bother you with this thing if the solution is simple as that.

Re: MediaMonkey v4.1.21.1867 Access Violation [#14897]

Posted: Fri Jun 29, 2018 5:35 am
by Ludek
Have you disabled also Player > DLNA settings > Accept input/control of MediaMonkey player via UPnP/DLNA ?

Re: MediaMonkey v4.1.21.1867 Access Violation [#14897]

Posted: Fri Jun 29, 2018 6:41 am
by ZvezdanD
Yes, I have.

Actually, I think that I know why is that happening and how to reproduce it. You should already have a database with at least one file that has a path on some media server.

After that, if you remove UPnP.dll, whenever you select some node in the Media Tree which contains that file, e.g. Entire Library, the program will be unresponsive or it will reset the computer (depending of the version, as I mentioned already). That will happen in the same events when the older versions of the program would display the mentioned error message if the UPnP.dll was not removed.

As I mentioned in the Mantis, that message appears "periodically every 10 seconds when the window is refreshing, e.g. after switching program or when the mouse is hovering above the main filelist.", so you could expect that the program without dll to become unresponsive in the same occasions.