Typically, once or twice a month, I go to the swap meet and by a bunch of music CDs. I use MediaMonkey to rip them onto my computer. I am not sure when this started happening; I do not believe that it was happening with version MediaMonkey_2024.0.0.3005. I think that I first started noticing it with version MediaMonkey_2024.0.0.3043; it was still happening with MediaMonkey_2024.0.0.3051. I did not test with MediaMonkey_2024.0.0.3053, nor have I yet tested with MediaMonkey_2024.0.0.3057. I will hopefully be able to test 3057 later this week – if so I will update this thread with the results. BTW, MM4 does not suffer from this problem.
My system has 64 GB of RAM and no other application experiences memory issues.
The problem (always happens):
Someplace after between 10 and 20 rips MediaMonkey crashes with an internal “out of memory” message.
Steps to reproduce:
Start repetitively ripping commercial music CDs; as uncompressed FLAC; <album artist>/<album>/<title>.
Workaround:
Use TaskManager to close crashed MediaMonkey 2024; delete all ripped tracks from the album which failed; restart MediaMonkey 2024 and start ripping again – starting with the album which failed.
“Out of memory” crash ripping multiple CDs [#21235]
Moderator: Gurus
“Out of memory” crash ripping multiple CDs [#21235]
–Edgar
64-bit Windows 10 MediaMonkey Lifetime Gold 3, 4 & beta5
Asus ASUS Prime X299-Deluxe motherboard
sound system: Soundcraft Signature 12 MTK mixer, JBL Eon 15 G2 speakers as mains and mains subs, and JBL Eon610 mains with Tascam LF-S8 sub as near field monitors at the computer
64-bit Windows 10 MediaMonkey Lifetime Gold 3, 4 & beta5
Asus ASUS Prime X299-Deluxe motherboard
sound system: Soundcraft Signature 12 MTK mixer, JBL Eon 15 G2 speakers as mains and mains subs, and JBL Eon610 mains with Tascam LF-S8 sub as near field monitors at the computer
Re: “Out of memory” crash ripping multiple CDs
Hi,
Can you try updating to build 3057? It includes some fixes to CD rip dialog.
Please let us know what happens.
Thanks!
Can you try updating to build 3057? It includes some fixes to CD rip dialog.
Please let us know what happens.
Thanks!
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: “Out of memory” crash ripping multiple CDs
I am running 3057 now, probably will not have time to test this until 3 or four days have passed…
–Edgar
64-bit Windows 10 MediaMonkey Lifetime Gold 3, 4 & beta5
Asus ASUS Prime X299-Deluxe motherboard
sound system: Soundcraft Signature 12 MTK mixer, JBL Eon 15 G2 speakers as mains and mains subs, and JBL Eon610 mains with Tascam LF-S8 sub as near field monitors at the computer
64-bit Windows 10 MediaMonkey Lifetime Gold 3, 4 & beta5
Asus ASUS Prime X299-Deluxe motherboard
sound system: Soundcraft Signature 12 MTK mixer, JBL Eon 15 G2 speakers as mains and mains subs, and JBL Eon610 mains with Tascam LF-S8 sub as near field monitors at the computer
Re: “Out of memory” crash ripping multiple CDs [#21235]
Hi Edgar,
fyi, we're able to replicate a memory leak with CD Ripping if verification is enabled.
Tracking at: https://www.ventismedia.com/mantis/view.php?id=21235
Thanks!
-Rusty
fyi, we're able to replicate a memory leak with CD Ripping if verification is enabled.
Tracking at: https://www.ventismedia.com/mantis/view.php?id=21235
Thanks!
-Rusty
Re: “Out of memory” crash ripping multiple CDs [#21235]
I inserted a music CD thus causing MediaMonkey_2024.0.0.3059_Debug to launch in CD ripping mode. I then ripped 26 CDs consecutively (without closing MediaMonkey) – the “out of memory” crash did not occur.
I consider this issue resolved.
However, something new showed up. I did not have un-ripped 26 CDs on hand so I ripped the 13 I had; then, I deleted all of those ripped tracks from my hard drive. I then re-ripped the same 13 CDs in reverse order. The first 18-19 rips went very smoothly; but, eventually MediaMonkey started “laboring” working harder and harder to rip the tracks that it had no trouble ripping before. Next week I will make sure that I have a large assortment of CDs to rip and will test this again.
I consider this issue resolved.
However, something new showed up. I did not have un-ripped 26 CDs on hand so I ripped the 13 I had; then, I deleted all of those ripped tracks from my hard drive. I then re-ripped the same 13 CDs in reverse order. The first 18-19 rips went very smoothly; but, eventually MediaMonkey started “laboring” working harder and harder to rip the tracks that it had no trouble ripping before. Next week I will make sure that I have a large assortment of CDs to rip and will test this again.
–Edgar
64-bit Windows 10 MediaMonkey Lifetime Gold 3, 4 & beta5
Asus ASUS Prime X299-Deluxe motherboard
sound system: Soundcraft Signature 12 MTK mixer, JBL Eon 15 G2 speakers as mains and mains subs, and JBL Eon610 mains with Tascam LF-S8 sub as near field monitors at the computer
64-bit Windows 10 MediaMonkey Lifetime Gold 3, 4 & beta5
Asus ASUS Prime X299-Deluxe motherboard
sound system: Soundcraft Signature 12 MTK mixer, JBL Eon 15 G2 speakers as mains and mains subs, and JBL Eon610 mains with Tascam LF-S8 sub as near field monitors at the computer
Re: “Out of memory” crash ripping multiple CDs [#21235]
I just sequentially ripped 31 CDs without closing and reopening MediaMonkey 3062. I did not experience the “out of memory” crash. I consider this resolved.
–Edgar
64-bit Windows 10 MediaMonkey Lifetime Gold 3, 4 & beta5
Asus ASUS Prime X299-Deluxe motherboard
sound system: Soundcraft Signature 12 MTK mixer, JBL Eon 15 G2 speakers as mains and mains subs, and JBL Eon610 mains with Tascam LF-S8 sub as near field monitors at the computer
64-bit Windows 10 MediaMonkey Lifetime Gold 3, 4 & beta5
Asus ASUS Prime X299-Deluxe motherboard
sound system: Soundcraft Signature 12 MTK mixer, JBL Eon 15 G2 speakers as mains and mains subs, and JBL Eon610 mains with Tascam LF-S8 sub as near field monitors at the computer