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

Issue 12340076: cc: Only create compositor context once. (Closed)

Created:
7 years, 10 months ago by danakj
Modified:
7 years, 10 months ago
Reviewers:
jamesr, piman
CC:
chromium-reviews, joi+watch-content_chromium.org, darin-cc_chromium.org, jam, apatrick_chromium, backer
Visibility:
Public.

Description

Only create compositor thread context once. The RenderWidgetCompositor asks the SharedContext3D to create its compositor thread context every frame. This causes us to destroy the old (valid) context, which tears down the CommandBufferProxyImpl on the main thread causing an assertion. We should only create a new context the first time we create the ContextProvider, ie only on first use and after a context loss. This change keeps the existing code from asserting, though the code will be replaced entirely soon by moving context ownership and the ContextProvider to RenderThreadImpl. R=jamesr,piman BUG=177768 Committed: https://src.chromium.org/viewvc/chrome?view=rev&revision=184736

Patch Set 1 #

Unified diffs Side-by-side diffs Delta from patch set Stats (+8 lines, -2 lines) Patch
M content/renderer/gpu/render_widget_compositor.cc View 2 chunks +8 lines, -2 lines 0 comments Download

Messages

Total messages: 4 (0 generated)
danakj
7 years, 10 months ago (2013-02-26 17:07:51 UTC) #1
piman
lgtm
7 years, 10 months ago (2013-02-26 17:51:51 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/12340076/1
7 years, 10 months ago (2013-02-26 17:52:36 UTC) #3
commit-bot: I haz the power
7 years, 10 months ago (2013-02-26 21:23:39 UTC) #4
Message was sent while issue was closed.
Change committed as 184736

Powered by Google App Engine
This is Rietveld 408576698