Chromium Code Reviews
chromiumcodereview-hr@appspot.gserviceaccount.com (chromiumcodereview-hr) | Please choose your nickname with Settings | Help | Chromium Project | Gerrit Changes | Sign out
(56)

Issue 12381042: cc: Only call didCompleteSwapBuffers() when in threaded mode. (Closed)

Created:
7 years, 9 months ago by danakj
Modified:
7 years, 9 months ago
Reviewers:
piman
CC:
chromium-reviews, cc-bugs_chromium.org, backer, slavi, jamesr
Visibility:
Public.

Description

cc: Only call didCompleteSwapBuffers() when in threaded mode. Swap buffers complete is the most confusing thing ever. Currently, the didCompleteSwapBuffers callbacks should only happen in threaded mode. In single thread mode, there is instead OnSwapBuffersCompleted which is somehow managed completely outside of the compositor. So, only call didCompleteSwapBuffers from the DelegatingRenderer if we're in thread mode. If we need some mode-agnostic notification we should use a new channel that doesn't have the confusing symantics of the swap buffers code. R=piman BUG=123444 Committed: https://src.chromium.org/viewvc/chrome?view=rev&revision=185586

Patch Set 1 #

Unified diffs Side-by-side diffs Delta from patch set Stats (+2 lines, -1 line) Patch
M cc/delegating_renderer.cc View 1 chunk +2 lines, -1 line 0 comments Download

Messages

Total messages: 4 (0 generated)
danakj
7 years, 9 months ago (2013-03-01 17:56:29 UTC) #1
piman
LGTM. I agree it's ridiculously, needlessly complicated.
7 years, 9 months ago (2013-03-01 18:01:27 UTC) #2
commit-bot: I haz the power
CQ is trying da patch. Follow status at https://chromium-status.appspot.com/cq/danakj@chromium.org/12381042/1
7 years, 9 months ago (2013-03-01 18:02:31 UTC) #3
commit-bot: I haz the power
7 years, 9 months ago (2013-03-01 20:16:49 UTC) #4
Message was sent while issue was closed.
Change committed as 185586

Powered by Google App Engine
This is Rietveld 408576698