I've seen what I think is the same bug on Webkit/Linux, and I traced it to the text-rendering CSS property. If you can replicate the glitch, try unsetting text-rendering.
It's unlikely anyone else will fix it, either. Linux Chrome doesn't get much love. (Alternatively, it gets a proportionate amount of love to the size of its userbase.)
I'm really sorry I never fixed it. I sometimes use Firefox on sites like this if the rendering really matters. You can also use a user stylesheet to unset it for all sites.
It would be amusingly relevant to the subject of the actual post if that feature was implemented in Chrome so you could conditionally turn this off just for the browser where it's broken. :)