Comment 20 for bug 1388612

I've just marked a lot of bugs as duplicates of this one, so that we can hopefully get to the bottom of the Great Gen4 Chrome Hang of 2014.

Firstly, apologies if your bug is not actually the same bug as all of the rest. It's hard to determine that in advance.

It looks like this report was the first, and it's from the end of June. What changed when you started experiencing the hang? Did you update Mesa, the kernel, or Chrome itself?

Does reverting to a version of one of these from, say, April avoid the problem? If so, that's great and we should be able to bisect it.