Hello guys,
A14A15B5
Now i can't open MM5 anymore.
And also close with Task Manager.
MediaMonkey 5.0.4.2656 and 2657 Alpha Portable Installation
Windows 10
i can't open MM5 (2656 and 2657) anymore
Moderator: Gurus
i can't open MM5 (2656 and 2657) anymore
Last edited by teodore on Mon Jul 25, 2022 12:40 pm, edited 1 time in total.
Windows 10 i7 8 Go - topping d30 - sansui au-222
Lyrics : http://www.mediamonkey.com/forum/viewto ... 0&p=448074
Lyrics : http://www.mediamonkey.com/forum/viewto ... 0&p=448074
Re: i can't open MM5 (2656 and 2657) anymore
Hi,
Delete Portable\Persistent.json and try again.
Delete Portable\Persistent.json and try again.
Best regards,
Peke
MediaMonkey Team lead QA/Tech Support guru
Admin of Free MediaMonkey addon Site HappyMonkeying
How to attach PICTURE/SCREENSHOTS to forum posts
Peke
MediaMonkey Team lead QA/Tech Support guru
Admin of Free MediaMonkey addon Site HappyMonkeying
How to attach PICTURE/SCREENSHOTS to forum posts
Re: i can't open MM5 (2656 and 2657) anymore
thank you for this reminder
Windows 10 i7 8 Go - topping d30 - sansui au-222
Lyrics : http://www.mediamonkey.com/forum/viewto ... 0&p=448074
Lyrics : http://www.mediamonkey.com/forum/viewto ... 0&p=448074
Re: i can't open MM5 (2656 and 2657) anymore
Hi,
My pleasure.
If it happens again it could be valuable to send us copy of corrupted persistent.json, so that we can see if it can be prevented.
My pleasure.
If it happens again it could be valuable to send us copy of corrupted persistent.json, so that we can see if it can be prevented.
Best regards,
Peke
MediaMonkey Team lead QA/Tech Support guru
Admin of Free MediaMonkey addon Site HappyMonkeying
How to attach PICTURE/SCREENSHOTS to forum posts
Peke
MediaMonkey Team lead QA/Tech Support guru
Admin of Free MediaMonkey addon Site HappyMonkeying
How to attach PICTURE/SCREENSHOTS to forum posts
Re: i can't open MM5 (2656 and 2657) anymore
Analyzing your crash log A14A15B5 and it looks like persistent.json deletion helped? As in the log I see that MM5 was trying to restore no longer existing action. I'll prevent this crash in the code for the next build.
BTW: Do you still have the original persistent.json to share it with us for analyzing?
BTW: Do you still have the original persistent.json to share it with us for analyzing?