@Jason: That recover is spilling out lots of text is normal, as it is quite brutally trying to skip some amount of data and continue reading.
The cause could also be a broken read, e.g. when the user logs out precicely while arbtt-capture is writing data, or maybe two arbtt-capture instances ran at the same time somehow... but none of this has ever happened here...
@Jason: That recover is spilling out lots of text is normal, as it is quite brutally trying to skip some amount of data and continue reading.
The cause could also be a broken read, e.g. when the user logs out precicely while arbtt-capture is writing data, or maybe two arbtt-capture instances ran at the same time somehow... but none of this has ever happened here...