On 2-Dec-08, at 12:11 PM, Sean M. Pappalardo wrote: > > > Albert Santoni wrote: >> Did Stanton verify this was occurring on Windows? > > No, but I just checked. It doesn't happen on Windows, only Linux. > (Can't > check Mac.) It would make testing a bit easier for me if I could get > it > to stop. :)
Ok, then there must be something silly going on in midiobjectalsaseq.cpp ... Looking at that file, I see that MidiObjectALSASeq::devClose() is conspicuously empty - We might not be closing the handle at all then, and ALSA might be closing it for us when Mixxx exits (and sending crazy stuff too). It looks like we want to close and free: m_input m_queue m_client m_handle pinfo Actually, it looks like we do some of these in the destructor in ~MidiObjectALSASeq(), but we're definitely not doing it right. We don't close/free all of the variables I listed above, and some of that should be done in devClose() because the other MIDI code calls devClose() and expects that we've closed our MIDI handles. Thanks, Albert ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ Mixxx-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/mixxx-devel
