Mixxx Leaks and Recovers Memory in cycles after Startup

[Marshall Conover]

After starting up Mixxx 1.10.0-beta1 in Windows 7 x64-bit, it will begin to use up a large chunk of memory, then drop it, then begin using it up again, and so on. Here's an image showing my memory usage after starting it: http://imgur.com/5aOLz

I do not have library scanning enabled at start-up, and my library is only 22 songs at the moment, all very small mp3's. My first thought was that it was memory leak that's being garbage collected, but it looks like the source code is C++, so I guess that's out the window.

If you'd like further information, just email me; I believe you can get that off of my launchpad account. I'd be willing to do some debugging/looking at the source code before handing it off to devs if it would help.

[Sean M. Pappalardo (pegasus-renegadetech)]

Would you please try the x86 version to see if it happens there too?

[Marshall Conover (marzhall-o)]

It does happen in x86 as well, but funny enough, the memory increase is about half the size before resetting: http://imgur.com/0S3Wm.

The first big bump in memory usage is the x64 beta, and the smaller bumps are the results of the x86 beta.

[RJ Skerry-Ryan (rryan)]

Huh.. interesting. Sorry for the hassle, but could you please try with
1.9.2?

Also, this is just sitting at idle after startup? Do you have any features
like recording, vinyl control, a MIDI controller, etc. activated?

Could you please try turning the waveforms on and off (Preferences ->
Interface -> Waveform option) to see if it's related to the OpenGL
waveforms?

Thanks for helping debug this,
RJ

On Tue, Nov 8, 2011 at 3:22 PM, Marshall Conover
<email address hidden>wrote:

> It does happen in x86 as well, but funny enough, the memory increase is
> about half the size before resetting: http://imgur.com/0S3Wm.
>
> The first big bump in memory usage is the x64 beta, and the smaller
> bumps are the results of the x86 beta.
>
> --
> You received this bug notification because you are a member of Mixxx
> Development Team, which is subscribed to Mixxx.
> https://bugs.launchpad.net/bugs/887664
>
> Title:
> Mixxx Leaks and Recovers Memory in cycles after Startup
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/mixxx/+bug/887664/+subscriptions
>

[Marshall Conover (marzhall-o)]

This occurs immediately after startup, with no features active, and it also occurred with the current versions available.

When I turned the waveforms off the memory cycle stopped, so it looks like that's the problem. I have a GTX 540M/Intel card Optimus setup for graphics.

[RJ Skerry-Ryan (rryan)]

It happens before loading any tracks, right?

[Marshall Conover (marzhall-o)]

That's correct; it also continues after I load tracks.

[ԜаӀtеr Ⅼарсһуnѕkі (wxl)]

For what it's worth (probably not much), running in a Windows 7 VM (latest Virtualbox with Guest Additions on OS X host), I did not have this problem. RJ did not think that I would see it given the fact that it is a VM, but upon further thought, given I do not have Direct 3D acceleration running, I would actually expect it to be more pronounced. I'm not sure in any case. I certainly have no way of emulating that particular card so that may be the problem. I wish someone with a standard Windows 7 install could check this out.

[Marshall Conover (marzhall-o)]

Well, on an install of 32-bit 9.x Mixxx on x64 7 on my dekstop, which has an Nivida GT(X?) 250, there were no memory problems. If you happen to have an idea of what to look at in the code, I have no problem doing some debugging; I just don't want to jump into the project with gdb and have no idea of how the project is structured or where to look. If you can point to a particular spot to tweak, however, I could take a look around. Otherwise, I suppose it's a niche bug probably having to do with the video drivers for my GPU, and as such something that will hit a small percentage of users.

[Daniel Schürmann (daschuer)]

I have just reported bug #890111 with maybe similar problems.
Setting QT_GL_USE_OPENGL1ENGINE=1 helps in this case. Maybe it helps here too.

[RJ Skerry-Ryan (rryan)]

Hey Marshall,

Did you ever get a chance to try this on 1.9.2?

Also, I have a new build of 1.10.0 that I'd appreciate you giving a shot. I think I may have figured it out but really am not sure since I can't reproduce it.

http://builds.mixxx.org/builds/release-1.10.x/mixxx-1.10.0-x64.exe

[RJ Skerry-Ryan (rryan)]

Oops, don't download yet. The build is updating. Make sure to download it
when its timestamp listed on this page is greater than now:
http://builds.mixxx.org/builds/release-1.10.x/<http://builds.mixxx.org/builds/release-1.10.x/mixxx-1.10.0-x64.exe>

On Sun, Dec 4, 2011 at 6:06 PM, RJ Ryan <email address hidden> wrote:

> Hey Marshall,
>
> Did you ever get a chance to try this on 1.9.2?
>
> Also, I have a new build of 1.10.0 that I'd appreciate you giving a
> shot. I think I may have figured it out but really am not sure since I
> can't reproduce it.
>
> http://builds.mixxx.org/builds/release-1.10.x/mixxx-1.10.0-x64.exe
>
> --
> You received this bug notification because you are a member of Mixxx
> Development Team, which is subscribed to Mixxx.
> https://bugs.launchpad.net/bugs/887664
>
> Title:
> Mixxx Leaks and Recovers Memory in cycles after Startup
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/mixxx/+bug/887664/+subscriptions
>

[Marshall Conover (marzhall-o)]

I apologize for taking so long. I see no memory issues in 1.10.0 x64, so the issue seems resolved. Thanks!

[Swiftb0y (swiftb0y)]

Mixxx now uses GitHub for bug tracking. This bug has been migrated to:
https://github.com/mixxxdj/mixxx/issues/6088