On Tue, 25 Mar 2008, Albert Santoni wrote: > > Mine generally die of Xlib errors or whatever around 2 hours.
> Have you gotten this Xlib error since I disabled the sidechain? (It looks like > your valgrind runs were from before I did that.) Well when I checked out 1895 the only thing changed was somethingsomethingengine.cpp (by faulty memory, I'm at work), and it was after your post re: disabling the sidechain, so I assume I got that edit. I didn't get to play with it long enough or seriously enough. Yesterday I assembled a car transmission instead :-) > > 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. > > Yeah, I wonder if disabling some of the keyboard event filtering stuff might > do the trick. Good thinking... (Could be something stupid like an > uninitialized variable causing this too...) Or a case where \0 or or undef or other outside-data-scope value gets handled funny? The valgrind website had some useful stuff, I'll look at it at work this week and play hopefulyl on Thursday. ------------------------------------------------------------------------- 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
