Crash/assertion failure playing to end of score
Not sure this crashes in a release build, but the debug build reports it fairly reliably. Just play the last few measures of the attached score, if it does fail the first time, it should the second or third.
Assertion failure is at the beginning of Score::setPos():
Q_ASSERT(tick <= lastMeasure()->endTick());
If I alter the code to let me set a breakpoint there, I see "tick" seems to be pretty strange, it's 77441/640. That's not really what I'd expect a valid fraction to look like, but beyond that, it's also just beyond the actual end of the score, which is 121 (77440/640).
Doesn't actually crash in release for me, but if we're setting a bad value based on this, maybe it leads to corruption later?
|Soon It's Gonna Rain.mscz||145.65 KB|