3 Jul
2010
3 Jul
'10
3:12 a.m.
On Mon, 2010-06-28 at 01:33 -0400, David Dillow wrote:
Ok, definitely different problem, as it dies 12:15 into a run using 2 periods per buffer, so the virtual timing code does not come into it. Interestingly enough, it died after ~44092 seconds while recording at 44100 Hz.
The patch should be applied. If and when I find the source of this new bug, I'll submit a separate patch.
For the Google record: this was the boundary wrap issue fixed by Clemens Ladisch in b406e6103baa3da85950f22d3d46d21a8da654c5. It's survived many boundary crossings with a shorted setting (256 seconds at 48kHz) so I'm very confident.
And I went with 2.6.34 to avoid the potential of instabilities in the 2.6.35-rc series. Oops :)