I just installed MediaMonkey on a new Windows 10 machine. I'm running the most recent version. I've been only working on subscribing to podcasts today and I am getting frequent "access violation" errors. I added permission to MM in my firewall software. Seemed to do okay for a while but then it started again. Always happens when I'm doing one of two things - 1) deleting a podcast episode or 2) trying to put information in a classification - custom field. I installed the debug software and was able to send the error log as instructed by the software. Anything else I need to do to be sure support has what it needs to take a look?

Thanks in advance!

Thanks guys, that registry edit fixed the problem

Hi,
Delete Current User -> Softare -> MediaMonkey -> Interface

>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?

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 ?

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?

If yes, then share your Portable folder.
If no then my suspection is that it could be rather related to UI state, so deleting MM interface in registry should this issue.

Hi,
Thx for LOG file.

I subscribed to all of podcasts from your log and had no issues updating/downloading/managing will send to developer for deeper analyze.

>2. have not received any PM or Emails from you.

Yep sorry, not sure if I missed anything about the new process but I couldn't raise a support ticket and neither could I send an attachment via the forum email. Anyhow, have sent you a PM with a file download link to the debug file. Thanks!

mtrhead wrote: ↑Sun Oct 04, 2020 1:03 pm Thanks for clarifying, ok
1) crash did not generate mediamonkey.elf file but I did submit an autolog with my email address and reference to this thread.
2) also ran debugview and will email log file "mediamonkey crash on podcast check".zip to you directly.

Just some peripheral info, interestingly latest beta version of MM5 did not crash against the same music database.

1. You will not be able to find ELF file is Auto send was done. You can copy crash log in to clipboard using details link in first debug screen where you enter email address
2. have not received any PM or Emails from you.

Re MM5: It is handling podcast bit differently due the different handling of podcasts.

Thanks for clarifying, ok
1) crash did not generate mediamonkey.elf file but I did submit an autolog with my email address and reference to this thread.
2) also ran debugview and will email log file "mediamonkey crash on podcast check".zip to you directly.

Just some peripheral info, interestingly latest beta version of MM5 did not crash against the same music database.

thanks for any pointers to help me fix this, at the moment MM4 is unusable.

Hi,
We can't tie specific Auto-Log to yours. Manual save of full debug log should be made according to https://www.mediamonkey.com/forum/viewt ... p?f=7&t=69 and you can send saved LOG DL link to me or lowlander in PM.

Mediamonkey has been stable for me for several years. Running 1910 and now have a permanent crash on startup whilst checking podcast subscriptions. It seems to consistently fall over at the point its checking new episodes of a podcast called "Reply All". I've run the debug version and submitted the crash report just now. I didn't see a specific resolution on this thread so I've added my instance of what looks like a similar problem.

The same goes, capture in a debug log (step 4b) and attach the log to a Support Ticket: https://www.mediamonkey.com/forum/viewt ... p?f=7&t=69

4.1.27 is also still crashing for me when downloading podcasts.

Lowlander wrote: ↑Tue Mar 10, 2020 9:55 am

CountZeroOr wrote: ↑Tue Mar 03, 2020 2:35 pmMediaMonkey Ver. is 4.1.26.1896

4.1.27?

If so, capture the problem in a debug log (step 4b) and attach the log to a Support Ticket: https://www.mediamonkey.com/forum/viewt ... p?f=7&t=69

I've done a few automatically submitted error logs from the debug version already.

CountZeroOr wrote: ↑Tue Mar 03, 2020 2:35 pmMediaMonkey Ver. is 4.1.26.1896

4.1.27?

If so, capture the problem in a debug log (step 4b) and attach the log to a Support Ticket: https://www.mediamonkey.com/forum/viewt ... p?f=7&t=69