The noteoff/crash bug seems to be due to a race condition between
AlsaDriver::startClocksApproved and the sequencer. I have a file that
usually reproduces the crash, and tracing it shows that the noteoff queue
looks fine until interrupted by
AlsaDriver::startClocksApproved/startClocks and from that point it says
"Bad address" every time.
Also valgrind reports (in a different run) cascading errors to a crash
about that time.
I think the relation between that and logical-instruments is that by
affecting the timing, I made the race condition finish a different way, so
it went from mostly harmless to serious. That's a guess at this point.
That's not an area of RG that I'm familiar with, so I want to run it by
everyone and ask for advice. Specifically, is it a reasonable solution to
delay the sequencer until the driver has completed its setup including
startClocks?
Tom Breton (Tehom)
------------------------------------------------------------------------------
Keep Your Developer Skills Current with LearnDevNow!
The most comprehensive online learning library for Microsoft developers
is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3,
Metro Style Apps, more. Free future releases when you subscribe now!
http://p.sf.net/sfu/learndevnow-d2d
_______________________________________________
Rosegarden-devel mailing list
[email protected] - use the link below to unsubscribe
https://lists.sourceforge.net/lists/listinfo/rosegarden-devel
