MediaMonkey v4.1.21.1867 Access Violation [#14897]

Post a reply


In an effort to prevent automatic submissions, we require that you complete the following challenge.
Smilies
:D :) :( :o :-? 8) :lol: :x :P :oops: :cry: :evil: :roll: :wink:

BBCode is ON
[img] is ON
[flash] is OFF
[url] is ON
Smilies are ON

Topic review
   

Expand view Topic review: MediaMonkey v4.1.21.1867 Access Violation [#14897]

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

by ZvezdanD » Fri Jun 29, 2018 6:41 am

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.

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

by Ludek » Fri Jun 29, 2018 5:35 am

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]

by ZvezdanD » Fri Jun 29, 2018 5:16 am

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]

by Ludek » Fri Jun 29, 2018 4:18 am

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]

by ZvezdanD » Thu Jun 28, 2018 2:26 pm

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]

by Ludek » Thu Jun 28, 2018 2:01 pm

Zvezdan, testing MediaMonkey.exe in build folder from another build will mostly cause issues, because not only the EXE is changing, but also the plugins and DLLs, so in short this isn't realiable method of testing that would make a sense.

I am also testing older builds, but I have each build installed in another folder like this:
C:\MediaMonkey 4.1.20.1864\
C:\MediaMonkey 4.1.21.1868\
C:\MediaMonkey 4.1.21.1870\
C:\MediaMonkey 4.1.21.1871\

This way I am sure that all DLLs and plugins are compatible with corresponding MM.exe

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

by ZvezdanD » Thu Jun 28, 2018 12:07 pm

Ludek wrote:
Thu Jun 28, 2018 7:28 am
If you don't want to see the message at all then just remove UPnP.dll entirely
Actually, this suggestion doesn't work. The program becomes unresponsive after a while. This is happening with 1866, 1867 and 1868, but not with 1737 and older that I tested.

Could you please tell me which was the last build which had UPnP.dll that doesn't check version of the program?

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

by ZvezdanD » Thu Jun 28, 2018 9:36 am

Here are the files that I have in the same folder:

Code: Select all

DeskPlayer.temp.0
MediaMonkey.chm
unins000.dat
DeskPlayer.dll
Equalize.dll
FastMM_FullDebugMode.dll
Gain.dll
hpCDBurn.dll
id3lib.dll
iPhoneCalc.dll
lame_enc.dll
libeay32.dll
libresample.dll
MMHelper.dll
mp3gain.dll
ogg.dll
PrimoBurner.dll
SQLite3_iOS8.dll
SQLite3MM.dll
ssleay32.dll
Unzip32.dll
vorbis.dll
WMAFunct.dll
WMAuth.dll
4gb_patch.exe
DBUpgrade.exe
Decoder.exe
MediaMonkey.exe
MediaMonkey (non-skinned).exe
MediaMonkey-1333-x.exe
MediaMonkey-1343-x.exe
MediaMonkey-1344-x.exe
MediaMonkey-1345-x.exe
MediaMonkey-1346-x.exe
MediaMonkey-1348-x.exe
MediaMonkey-1349-x.exe
MediaMonkey-1351-x.exe
MediaMonkey-1352-x.exe
MediaMonkey-1358-x.exe
MediaMonkey-1364-u.exe
MediaMonkey-1365-u.exe
MediaMonkey-1367-u.exe
MediaMonkey-1368-u.exe
MediaMonkey-1383-u.exe
MediaMonkey-1389-u.exe
MediaMonkey-1391-u.exe
MediaMonkey-1392-u.exe
MediaMonkey-1394-u.exe
MediaMonkey-1395-u.exe
MediaMonkey-1422-u.exe
MediaMonkey-1436-u.exe
MediaMonkey-1442-u.exe
MediaMonkey-1459.exe
MediaMonkey-1466.exe
MediaMonkey-1470.exe
MediaMonkey-1501.exe
MediaMonkey-1504.exe
MediaMonkey-1511.exe
MediaMonkey-1609.exe
MediaMonkey-1646.exe
MediaMonkey-1650.exe
MediaMonkey-1652.exe
MediaMonkey-1656.exe
MediaMonkey-1658.exe
MediaMonkey-1661.exe
MediaMonkey-1662.exe
MediaMonkey-1683.exe
MediaMonkey-1703.exe
MediaMonkey-1737.exe
MediaMonkey-1867.exe
MediaMonkey-1868.exe
MediaMonkey64Helper.exe
MediaMonkeyService.exe
MediaMonkeyVHelper.exe
unins000.exe
UninstDP.exe
VisHelper.exe
winamp.exe
WinAmp.ini
QTSource.lic
readme.txt
whatsnew.txt
MediaMonkey.url
UPnP.dll.z
I could start any of these MediaMonkey-xxxx.exe files just by double-click. These builds that have -u and -x in suffix have some strange behaviors with enlarged fonts. These builds that have -x in suffix additionally display some error on the startup, but after that they work fine at least for testing my scripts with them.

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

by ZvezdanD » Thu Jun 28, 2018 9:25 am

Ludek wrote:
Thu Jun 28, 2018 7:28 am
What's strange about the fact that the interface between UPnP.dll and MM.exe was updated?
It is strange because it worked fine without that message until recently. I don't know exactly in which build that message started to appear.
Ludek wrote:
Thu Jun 28, 2018 7:28 am
If you don't want to see the message at all then just remove UPnP.dll entirely
Ok, thanks for the hint. I didn't expect it will work with that file removed.
Ludek wrote:
Thu Jun 28, 2018 7:28 am
or copy the UPnP.dll corresponding to the given MediaMonkey.exe (i.e. UPnP.dll from the same build as MediaMonkey.exe)
It seems you didn't understand my explanation. I have a bunch of the MediaMonkey-xxxx.exe files from different builds in the _same_ folder and I can start any of them without reinstalling that particular build, but all other files in that folder are from the latest installed version (dlls and such). I cannot have a bunch of UPnP_xxxx.dll files in the same folder. Well, I can, but exe will not link to them, but only to UPnP.dll.

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

by Ludek » Thu Jun 28, 2018 7:28 am

ZvezdanD wrote:
Thu Jun 28, 2018 7:08 am
Ludek wrote:
Thu Jun 28, 2018 6:13 am
That's ok, this is just that you copied MM.EXE from another build that is not compatible with UPnP.dll from older build.
That is not OK, as I explained here: https://www.ventismedia.com/mantis/view.php?id=14870
What's strange about the fact that the interface between UPnP.dll and MM.exe was updated? If you don't want to see the message at all then just remove UPnP.dll entirely or copy the UPnP.dll corresponding to the given MediaMonkey.exe (i.e. UPnP.dll from the same build as MediaMonkey.exe)

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

by ZvezdanD » Thu Jun 28, 2018 7:08 am

Ludek wrote:
Thu Jun 28, 2018 6:13 am
That's ok, this is just that you copied MM.EXE from another build that is not compatible with UPnP.dll from older build.
That is not OK, as I explained here: https://www.ventismedia.com/mantis/view.php?id=14870

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

by Ludek » Thu Jun 28, 2018 6:13 am

My original problem seems to be fixed with this version :)
Thanks for confirmation.
although it is very, very slow monitoring all my files (tracks). But, I also noticed it being very slow with other debug versions. Maybe it's just a debug issue.
Yes, debug builds are slower (especially when DbgView is started)
I also get this UPnP.dll error.
That's ok, this is just that you copied MM.EXE from another build that is not compatible with UPnP.dll from older build.
We are going to post another RC (1872), so just install build 1872 to that folder to fix the issue. It will be posted hopefully today (I am just revising one more issue).

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

by Stigg » Wed Jun 27, 2018 8:12 pm

Here is the new log.

My original problem seems to be fixed with this version :), although it is very, very slow monitoring all my files (tracks). But, I also noticed it being very slow with other debug versions. Maybe it's just a debug issue.

I also get this UPnP.dll error.
Error: UPnP.dll is not compatible with this version of MediaMonkey! Reinstall MediaMonkey.
Image

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

by Ludek » Wed Jun 27, 2018 3:10 am

Thanks for the logs, I've analyzed the logs and it seems to confirm my experiences and test results described above (note that my startup times were better because I haven't started DbgView).

Based on your logs:
- with 1864 it took 12 seconds to show the main window (with scripts loaded)
- with 1871 it took 10 seconds to show main window and scripts were loading for 2 seconds

So the overal time is nearly the same, but in case of 1871 there were the blank panels with progress "Loading... scriptNameX.vbs" shown for 2 seconds.
Can you confirm?

Could you please also replace your current MediaMonkey.exe (from build 1871) by this one:
https://www.dropbox.com/s/q0e0phjxptl7u ... y.exe?dl=0
And generate one more log? It should improve the loading time and experience slightly.

Thanks!

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

by Stigg » Tue Jun 26, 2018 8:45 pm

Here they are.
They're big. 10 MB each.

I have zipped them up, and you can download it here.

Top