Bug 73929 - [chromium] Hitting assertion in CCSchedulerStateMachine::updateState
Summary: [chromium] Hitting assertion in CCSchedulerStateMachine::updateState
Status: RESOLVED WORKSFORME
Alias: None
Product: WebKit
Classification: Unclassified
Component: WebCore Misc. (show other bugs)
Version: 528+ (Nightly build)
Hardware: Unspecified Unspecified
: P2 Normal
Assignee: Nobody
URL:
Keywords:
Depends on:
Blocks: 72738
  Show dependency tree / graph
 
Reported: 2011-12-06 09:52 PST by Iain Merrick
Modified: 2011-12-06 13:05 PST (History)
3 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Iain Merrick 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.
Comment 1 James Robinson 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?
Comment 2 Iain Merrick 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.
Comment 3 James Robinson 2011-12-06 11:52:03 PST 
Is the version of WebKit you are testing earlier than 101911 (it's in about:version)?
Comment 4 Iain Merrick 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.
Comment 5 James Robinson 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.