Macbook Model = 14" Apple M3 Pro chip with 18gb memory
Mac OS = Tahoe 26.5.1 (25F80)
MediaMonkey version = 2027.0.0.3512 (2026-06-16)
When I try to create a report using File > Reports > File list, the program just shuts down without an error or debug message being displayed. Is there a way that I can get a debug log to send you that shows why it shut down?
Thanks
Matt
MM shuts down when trying to create a file list
Moderator: Gurus
Re: MM shuts down when trying to create a file list
Please see this sticky post: viewtopic.php?t=109505
Download MediaMonkey ♪ License ♪ Knowledge Base ♪ MediaMonkey for Windows 2024 Help ♪ MediaMonkey for Android Help
Lowlander (MediaMonkey user since 2003)
Lowlander (MediaMonkey user since 2003)
Re: MM shuts down when trying to create a file list
Hi Lowlander,
Yes, I did this see that post and it says "Debug logs can be generated automatically in case of crashes, but otherwise must be manually generated. To do so in MediaMonkey for macOS, trigger the issue and then click Help > Debug > Send logs.". The problem I have is that because MM has shut down when I tried to create the file list, there is no "Help > Debug > Send" option to go into.
Or can I do that once I open MM back up again? Will the "Help > Debug > Send" data relate to the session that got closed down or just the current session I'm in that won't have had any crashes yet because I've just reopened MM?
Sorry if these are naive questions, but I've never been involved in any testing before and am not sure how the whole debugging stuff works.
Thanks
Matt
Yes, I did this see that post and it says "Debug logs can be generated automatically in case of crashes, but otherwise must be manually generated. To do so in MediaMonkey for macOS, trigger the issue and then click Help > Debug > Send logs.". The problem I have is that because MM has shut down when I tried to create the file list, there is no "Help > Debug > Send" option to go into.
Or can I do that once I open MM back up again? Will the "Help > Debug > Send" data relate to the session that got closed down or just the current session I'm in that won't have had any crashes yet because I've just reopened MM?
Sorry if these are naive questions, but I've never been involved in any testing before and am not sure how the whole debugging stuff works.
Thanks
Matt