RESOLVED WORKSFORME 73929
[chromium] Hitting assertion in CCSchedulerStateMachine::updateState 
https://bugs.webkit.org/show_bug.cgi?id=73929
Summary [chromium] Hitting assertion in CCSchedulerStateMachine::updateState
Iain Merrick
Reported 2011-12-06 09:52:21 PST
To reproduce, launch Chromium with --force-compositing-mode --enable-threaded-compositing. Open http://diden.net/test/tex.html in two tabs and switch back and forth between them. Both tabs hit an assert fairly quickly: ASSERTION FAILED: m_needsCommit third_party/WebKit/Source/WebCore/platform/graphics/chromium/cc/CCSchedulerStateMachine.cpp(109) : void WebCore::CCSchedulerStateMachine::updateState(WebCore::CCSchedulerStateMachine::Action) Can't seem to get a full stack trace, even with --disable-seccomp-sandbox.
Attachments
Add attachment proposed patch, testcase, etc.
James Robinson
Comment 1 2011-12-06 11:47:40 PST
This looks a lot like what https://bugs.webkit.org/show_bug.cgi?id=73351 fixed in http://trac.webkit.org/changeset/101911 - is your build out of date?
Iain Merrick
Comment 2 2011-12-06 11:50:50 PST
Hmm, shouldn't be, as I was hitting it on ToT synced today. I reproduced on a straight Chrome build, though, so maybe its WebKit is slightly behind.
James Robinson
Comment 3 2011-12-06 11:52:03 PST
Is the version of WebKit you are testing earlier than 101911 (it's in about:version)?
Iain Merrick
Comment 4 2011-12-06 11:54:28 PST
Just checked the actual code, I don't have that patch yet. I'll see if I can find a different repro case, or close this if not.
James Robinson
Comment 5 2011-12-06 13:05:21 PST
OK. The repro steps don't happen for me with that patch, so I'm going to presume this is fixed. Feel free to reopen or file a new bug if you find a case that's still broken.
Note You need to log in before you can comment on or make changes to this bug.