Threading is hard (for me).
This page: http://www.kevs3d.co.uk/dev/canvasmark/ always hits the RELEASE_ASSERT added in r168493 when running the benchmark.
However! It's a total lie; we're getting didUpdate back from the UI process on the Web process's main thread while the Web process's CommitQueue is *in between* sendMessage() and setting m_hasFlushed.
So, we assert.
I'm going to move resetting m_hasFlushed *before* sendMessage(), because we really only care about asserting if we start flushing again before we have flushed the contexts; sendMessage() doesn't really have any bearing on flushing correctness.
Created attachment 231235 [details]
Comment on attachment 231235 [details]
Clearing flags on attachment: 231235
Committed r168589: <http://trac.webkit.org/changeset/168589>
All reviewed patches have been landed. Closing bug.