Memory leak in 4.0.7.1511 and 1672

RandomEngy · Post by **RandomEngy** » Mon Nov 25, 2013 1:32 pm

I boot up MediaMonkey and start listening to some podcasts and the memory usage climbs until it hits around 3GB, then it crashes. I've installed a debug build to try and report the error but I can't tell if it's getting through. It just seems to spawn another error report dialog after I try to send the first one. There isn't anything in the EurekaLog folder.

Using MM 4.0.7.1511 on Windows 8.1 x64.

nohitter151 · Post by **nohitter151** » Mon Nov 25, 2013 1:35 pm

http://www.mediamonkey.com/forum/viewtopic.php?f=7&t=69

dtsig · Post by **dtsig** » Mon Nov 25, 2013 1:38 pm

RandomEngy, I could be really off here but I don't think you should be running 4.0.7. anything on win8. Get the beta from the app store and run it. Either the MMW (full) which currently in beta at 1672, or the err .. metro version. They really have a lot of changes, enhancments for Win 8

RandomEngy · Post by **RandomEngy** » Mon Nov 25, 2013 5:12 pm

nohitter151 wrote:http://www.mediamonkey.com/forum/viewtopic.php?f=7&t=69

Yes, I read that. That's why I downloaded the debug version and tried to get the error report. Is there something in particular that I missed?

dtsig wrote:RandomEngy, I could be really off here but I don't think you should be running 4.0.7. anything on win8. Get the beta from the app store and run it. Either the MMW (full) which currently in beta at 1672, or the err .. metro version. They really have a lot of changes, enhancments for Win 8

Thanks for the pointer. The beta seems to be behaving itself for now. Going to pass on the metro version; I like my taskbar too much.

dtsig · Post by **dtsig** » Mon Nov 25, 2013 5:59 pm

Oh wait ... it's "New Windows"

agreed on metro versions

RandomEngy · Post by **RandomEngy** » Sun Dec 01, 2013 2:13 pm

I spoke too soon. This is also happening in 4.1.0.1672. Going to install the debug version and see if this actually succeeds in generating an error report.

RandomEngy · Post by **RandomEngy** » Thu Dec 05, 2013 11:58 am

Okay I've submitted a few crash reports on 1672 and linked to this topic. I don't know which ones went through because it can give 2-3 crash report windows consecutively (and I am left wondering if the crash reporter crashed).

Post by **Lowlander** » Thu Dec 05, 2013 12:45 pm

You should capture it in a debug log with DBGView and then attach it to a support ticket so you can track its status.

nohitter151 · Post by **nohitter151** » Thu Dec 05, 2013 11:41 pm

Are you using any addons?

RandomEngy · Post by **RandomEngy** » Mon Dec 09, 2013 12:12 pm

I'm not using any addons. I've submitted a support ticket and attached the DbgView log.

RandomEngy · Post by **RandomEngy** » Thu Dec 12, 2013 6:40 pm

An update: I got a response from the support ticket and resolved the issue. Apparently the tab for my podcast thought it had 300,000 items and was trying to generate art for the art browser for all of them. Weird since that podcast has maybe 300 items and my whole music library has 3000. In any event changing the view to not include the art fixed it.

Memory leak in 4.0.7.1511 and 1672

Memory leak in 4.0.7.1511 and 1672

Re: Memory leak in 4.0.7.1511

Re: Memory leak in 4.0.7.1511

Re: Memory leak in 4.0.7.1511

Re: Memory leak in 4.0.7.1511

Re: Memory leak in 4.0.7.1511

Re: Memory leak in 4.0.7.1511 and 1672

Re: Memory leak in 4.0.7.1511 and 1672

Re: Memory leak in 4.0.7.1511 and 1672

Re: Memory leak in 4.0.7.1511 and 1672

Re: Memory leak in 4.0.7.1511 and 1672