I was actually experiencing this issue on the dev build of Chrome (both Mac and Windows) for the past few months but the latest update this week to v30 seems to have fixed it for me. Clearing cache all that didn't do a thing beforehand. I had to use Firefox.