That behaviour was present for five or ten minutes while I was implementing it; it was sending you to a page starting right after the last post in the thread. I replaced it with the logic used by the thread list to determine the first unread post. That's well-tested code that shouldn't cause any such issue.