I've never run into this bug myself, and our users have never reported it either as far as I know. While it sounds like Chrome is crap from those threads I still find it hard to believe they'd leave a bug like that for 3 years...
Anyway, post relevant code and I'll see if I can duplicate the error.