Comment 3 for bug 392745

I was having the same issue, with an almost identical backtrace. My solution was to remove all of the data in the session directory. This way when rtorrent starts up again it performs the hash check from the very beginning. I vaguely recall reading about this solution (if you'd call it that) on the rtorrent bug tracker.