Page 1 of 1
Application errors (regression 3200?)
Posted: Tue Dec 30, 2025 2:53 pm
by tbm72
Getting lots of these errors when I add new music to my library. Only since the new update (2024.2.1.3200) so presumably a regression bug?

Re: Application errors
Posted: Tue Dec 30, 2025 3:02 pm
by tbm72
And another when editing an album's properties:

Re: Application errors
Posted: Tue Dec 30, 2025 3:04 pm
by tbm72
I'm going back to an older version, this one is way too buggy and crashing all the time with these errors.
Re: Application errors
Posted: Tue Dec 30, 2025 3:17 pm
by Lowlander
Please capture this in a debug lig (step 4b) and attach the log to a Support Ticket:
https://www.mediamonkey.com/forum/viewtopic.php?t=86643
Re: Application errors
Posted: Tue Dec 30, 2025 3:23 pm
by tbm72
Sorry, don't have time at the moment so have just gone back to the previous stable version.
Re: Application errors
Posted: Thu Jan 01, 2026 7:14 pm
by Peke
tbm72 wrote: ↑Tue Dec 30, 2025 3:23 pm
Sorry, don't have time at the moment so have just gone back to the previous stable version.
Interesting, Only Change to Rating handling in 3200 is related to
https://www.ventismedia.com/mantis/view.php?id=21880 so even I can't replicate I wonder if that is the case and it is really regression. Debug log would be very useful here.
Re: Application errors (regression 3200?)
Posted: Sat Jan 10, 2026 10:10 am
by tbm72
Same error in latest 3201 beta:
Going back to stable again where I don't get these errors
Re: Application errors (regression 3200?)
Posted: Thu Jan 29, 2026 4:59 pm
by rusty
Hi tbm72,
We're getting ready for an RC.
We've never managed to replicate this bug but I want to make sure that it's fixed. Do you have some time to verify whether it still occurs for you with 3206? And if it does, would you be able to share a debug log of the issue?
Thanks!
-Rusty
EDIT: The issue was actually fixed in 3207, so please hold off on testing until we post this weekend's new build. Thx!
Re: Application errors (regression 3200?)
Posted: Fri Jan 30, 2026 7:42 am
by Ludek
FYI: this error was fixed in the latest build (3207+).