It looks like at least some cases of this problem were fixed by an update to Google Chrome (to 38.0.2125.111) that was released earlier this week. This has been a long running issue with the chromium code underlying Chrome, with many, many hundreds of complaints on the chromium development boards, so I wouldn't claim that it hit all of them.
One thing that helped me when I was having this problem with the previous build was running an ad blocker on the offending pages. It looked to me like there may have been code in, ironically, Google's DoubleClick ad network that would trigger the bug. At any rate, this might be worth trying if you are still seeing issues with Google Chrome.