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

Issue 7828046: Reland 98392 - Split WebGraphicsContext3DCommandBufferImpl::initialize() into two stages. (Closed)

Created:
9 years, 3 months ago by lain Merrick
Modified:
9 years, 3 months ago
CC:
chromium-reviews, joi+watch-content_chromium.org, darin-cc_chromium.org, jam, apatrick_chromium
Visibility:
Public.

Description

Reland 98392 - Split WebGraphicsContext3DCommandBufferImpl::initialize() into two stages. After the context is created, the remaining calls should be done on the compositor thread. This CL adds a MaybeInitializeGL() method, which we run on each call to makeContextCurrent(). Added asserts to RendererGLContext to check that it's always used on the same thread. Original review URL: http://codereview.chromium.org/7713015 Reverted due to buildbot errors: http://codereview.chromium.org/7745042 Committed: http://src.chromium.org/viewvc/chrome?view=rev&revision=99648

Patch Set 1 #

Total comments: 2

Patch Set 2 : '' #

Unified diffs Side-by-side diffs Delta from patch set Stats (+113 lines, -59 lines) Patch
M content/renderer/gpu/renderer_gl_context.h View 1 1 chunk +4 lines, -0 lines 0 comments Download
M content/renderer/gpu/renderer_gl_context.cc View 1 5 chunks +9 lines, -1 line 0 comments Download
M content/renderer/gpu/webgraphicscontext3d_command_buffer_impl.h View 1 4 chunks +17 lines, -0 lines 0 comments Download
M content/renderer/gpu/webgraphicscontext3d_command_buffer_impl.cc View 1 7 chunks +83 lines, -58 lines 0 comments Download

Messages

Total messages: 5 (0 generated)
lain Merrick
Second attempt to land this CL. Not sure what went wrong last time, but I'll ...
9 years, 3 months ago (2011-09-02 16:57:55 UTC) #1
jbates
comments LGTM
9 years, 3 months ago (2011-09-02 17:02:02 UTC) #2
Ken Russell (switch to Gerrit)
LGTM http://codereview.chromium.org/7828046/diff/1/content/renderer/gpu/webgraphicscontext3d_command_buffer_impl.cc File content/renderer/gpu/webgraphicscontext3d_command_buffer_impl.cc (right): http://codereview.chromium.org/7828046/diff/1/content/renderer/gpu/webgraphicscontext3d_command_buffer_impl.cc#newcode123 content/renderer/gpu/webgraphicscontext3d_command_buffer_impl.cc:123: TRACE_EVENT0("gpu", "WebGfxCtx3DCmdBfgImpl::MaybeInitializeGL"); Bfg?
9 years, 3 months ago (2011-09-02 17:56:46 UTC) #3
lain Merrick
http://codereview.chromium.org/7828046/diff/1/content/renderer/gpu/webgraphicscontext3d_command_buffer_impl.cc File content/renderer/gpu/webgraphicscontext3d_command_buffer_impl.cc (right): http://codereview.chromium.org/7828046/diff/1/content/renderer/gpu/webgraphicscontext3d_command_buffer_impl.cc#newcode123 content/renderer/gpu/webgraphicscontext3d_command_buffer_impl.cc:123: TRACE_EVENT0("gpu", "WebGfxCtx3DCmdBfgImpl::MaybeInitializeGL"); On 2011/09/02 17:56:46, kbr wrote: > Bfg? ...
9 years, 3 months ago (2011-09-05 10:37:53 UTC) #4
lain Merrick
9 years, 3 months ago (2011-09-05 13:44:08 UTC) #5
Well, I finally found out what caused that error! Stupid oversight -- the
DCHECKs don't compile in release mode. The try bots didn't catch this but the
build bots did.

Ken, I've TBR'd a fix on you - http://codereview.chromium.org/7834021/

Powered by Google App Engine
This is Rietveld 408576698