I went back to MediaMonkey v4.1.20.1864, and all is good again.
Access violation at address 00A245C0 in module 'MediaMonkey.exe'. Read of address 00000020.
Moderator: Gurus
Access violation at address 00A245C0 in module 'MediaMonkey.exe'. Read of address 00000020.
I don't get the Access Violation error now, but it is now very slow to start.Ludek wrote: ↑Fri Jun 01, 2018 1:59 am Could you please try with build 1868 and report whether the issue is resolved for you?
https://www.mediamonkey.com/forum/viewt ... 0b#p445758
I cannot replicate, are you saying that it is slower to start with comparing to 1867 or comparing to 1864?
Thanks, I can replicate this, to be fixed as https://www.ventismedia.com/mantis/view.php?id=14897The art browser with details has to be manually re-enabled.
Here are the addons that I have installed.
Do I still use DebugView with the MediaMonkey Debug versions?Ludek wrote: ↑Sun Jun 24, 2018 3:33 pm Hi Stigg,
thank you very much for your feedback.
Unfortunately the debug logs don't include any MediaMonkey messages, they were probably generated using the release build, could you please download and install debug builds and generate them again?
1864 debug: http://www.mediamonkey.com/beta/MediaMo ... _Debug.exe
1871 debug: http://www.mediamonkey.com/beta/MediaMo ... _Debug.exe
Thanks!
Thanks, I can replicate this, to be fixed as https://www.ventismedia.com/mantis/view.php?id=14897