by mtrhead » Wed Oct 07, 2020 5:14 pm
>Hi, in the debug log I don't see an exception, but after the podcast update has finished the log stops (without attempt to close MM in the log) -- so >you either saved the DbgView output without closing MM or MM has frozen?
Yes it froze with access violation at address 00000000 Write of address 00000000
>You indicated that you submitted a crash log, but the only crash logs from 1913 here is from user email starting with johnquintas, is this your email address ?
per my thread I was running 1910 and did the debug, though it failed through version 1914 when I upgraded.
>Try to install 1914 as portable version (and copy your MM.DB located in C:\Users\alanx\AppData\Roaming\MediaMonkey\ to the Portable folder inside the MediaMonkey install folder) to see whether you can still replicate the issue?
Ok, this test worked fine, no crash at all
>If no then my suspection is that it could be rather related to UI state, so deleting MM interface in registry should this issue.
OK... I didn't want to poke around in the registry too much though I'm familiar with regedit, can you tell me how specifically to do this thanks
>Hi, in the debug log I don't see an exception, but after the podcast update has finished the log stops (without attempt to close MM in the log) -- so >you either saved the DbgView output without closing MM or MM has frozen?
Yes it froze with access violation at address 00000000 Write of address 00000000
>You indicated that you submitted a crash log, but the only crash logs from 1913 here is from user email starting with johnquintas, is this your email address ?
per my thread I was running 1910 and did the debug, though it failed through version 1914 when I upgraded.
>Try to install 1914 as portable version (and copy your MM.DB located in C:\Users\alanx\AppData\Roaming\MediaMonkey\ to the Portable folder inside the MediaMonkey install folder) to see whether you can still replicate the issue?
Ok, this test worked fine, no crash at all
>If no then my suspection is that it could be rather related to UI state, so deleting MM interface in registry should this issue.
OK... I didn't want to poke around in the registry too much though I'm familiar with regedit, can you tell me how specifically to do this thanks