Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[TRS38]

HI from France

Since I have installed last version of MC , memory of my Mac MINI discrease during playing and totally use the memory...after 2 h.!!!
I have 8 Gb memory installed and as soon I quit MC....memory increase immediately!!!

If I play more than 2h...system became very very very slow!!

Someone have same problem?

Regards

Jacques

[1spammagnet@gmail.com]

I have 16gb on my Mac Mini and after a couple of hours the music will start stuttering and then it'll completely stop and all I'll hear is static. I'll get a dialog box that says MC19 has used too much application memory.

[TRS38]

Same like me!

I hope someone can help us!

[JimH]

It appears to be a problem introduced in this build.  Please download an older build until we can get it fixed.

[TRS38]

Thanks for your answer.

I will install an older one.

Waiting for the new one

Regards

Jacques

[jmrdc]

Same problem, only when playing hi-res files.  I have 12GB memory (7GB nominally usable) on a MacPro, but get about 2hrs continuous playback before it goes down to about +/- 500 MB of memory.  I'll wait.  Thanks for all you do.

[bplexico]

Ok, so I took an album of redbook files and decided to have them all output at 2 x DSD. After 3 songs, 14 minutes memory usage by Media Center 19 is up to 1.62 GB and climbing....I am going to keep it running overnight to see if and when I get an error and will then send a log file.

Update - after 30 minutes memory usage is up to 2.71 GB.

Update - after 39 minutes memory usage is up to 3.38 GB...

More later.

[mwheelerk]

I have just experienced the shutdown due to MC running out of memory. I am on Mavericks and have 8GB RAM. I have been playing music for about 90 minutes and at the same time I have bee editing tags within Genres. The first thing I started to notice as I was making tags after about 60 minute the music began to stutter while I was selecting the tag changes. Finally it just crashed.

I think I will revert back to the previous version and wait for the next fix to resolve this memory hog issue.

[bplexico]

Ok 9 hours later. MC still playing away.

Attached is a snapshot of Activity Monitor with memory usage up to 4.91 GB. Virtual memory is up to 39 GB. And another after having quit MC>


Update - Ok - apparently playing DSD files accelerates the condition as I beach balled pretty fast when doing so. I know you folks are working to fix, so thank you!
 

[TRS38]

It will be correct in the next build

Thanks to all for sharing experience

Jacques

[JohnT]

Please install the latest build at the top of this page (currently .84).  This should fix the memory issue.  If you still have problems, let us know.

[TRS38]

Hi from France

I think the memory issue is not perfectly done....
Free Memory steel decrease  more slowly than the on the previous version but steel.

After 4 hours....only 800 Mb free memory....6,4 Gb when start listening.
No anther application running.
and steel decrease....

Regards

Jacques ?

[JohnT]

Hi from France

I think the memory issue is not perfectly done....
Free Memory steel decrease  more slowly than the on the previous version but steel.

After 4 hours....only 800 Mb free memory....6,4 Gb when start listening.
No anther application running.
and steel decrease....

Regards

Jacques ?

In Activity Monitor, can you watch just the number reported for the Media Center application?  That's the one that would increase steadily if there's a leak.

[TRS38]

Hi

I watched on system activity.
MC is well between 100 and 330 MB...
It turn all the night without any trouble.
So all is ok I think.

Sorry for my first diagnostic

Regards

Jacques

[JohnT]

Thanks for letting us know.

[jmrdc]

This may not be a problem other than user error, or something I don't understand…

Last night I let a playlist run all night (10 hrs) and when I woke I was down to 386MB of RAM.  The dump in .84 fixed the glaring problem, but it seems it's still chomping a lot of memory.  Is this normal, or is there another culprit?  No other programs or processes were running, outside of normal background programs that do not eat away that much RAM.