On Tue, 25 Mar 2008, Albert Santoni wrote: > Some of these big leaks are probably occurring at exit.
Duh, of course. I know all mem is recovered when the process closes. > I haven't seen Mixxx > leak a crippling large amount of memory in ~2 hour sessions Mine generally die of Xlib errors or whatever around 2 hours. > > Oddly, when I do this mixxx comes fully up, then immediately > > quits "normally" eg. Control-Q clean exit. As soon as the GUI > > is fully drawn, the dialog "writing song database" appears, > > then it quits. > > Yeah, this is the same problem I have. I thought it was something I was doing > wrong. Does this happen every time for you, or is there something you can do > to mitigate it? We need a valgrind run where a few songs are loaded and played > so we can detect memory corruption inside the mixing engine... Every time, and I've found no way so far to stop it. Is the call to see keyboard events funny? It appears casually to be the very first instance where a Control-Q or File->Quit could be manually entered. > These runs give me something useful to get started with, thanks again. If we > can figure out how to get Mixxx to not exit after it starts under valgrind, > then we should be able to get even more useful data. I will RTFM and see if I can find anything to try. ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ Mixxx-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/mixxx-devel
