New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 640684 link

Starred by 1 user

Issue metadata

Status: Assigned
Owner:
OOO until 2019-01-24
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Mac
Pri: 3
Type: Bug

Blocked on:
issue 612542



Sign in to add a comment

conformance_textures_webgl_canvas_tex_2d_rgba_rgba_unsigned_short_4_4_4_4 failure on Mac Retina

Project Member Reported by vmp...@chromium.org, Aug 24 2016

Issue description

[15429:1295:0824/103105:FATAL:DrawingBuffer.cpp(676)] Check failed: produceSyncToken.HasData(). 
0   Chromium Framework                  0x000000011021ead3 base::debug::StackTrace::StackTrace() + 19
1   Chromium Framework                  0x0000000110240b07 logging::LogMessage::~LogMessage() + 71
2   Chromium Framework                  0x00000001132e4be2 blink::DrawingBuffer::copyToPlatformTexture(gpu::gles2::GLES2Interface*, unsigned int, unsigned int, unsigned int, int, bool, bool, blink::SourceDrawingBuffer) + 530
3   Chromium Framework                  0x00000001149f3b5a blink::WebGLRenderingContextBase::texImageCanvasByGPU(blink::HTMLCanvasElement*, unsigned int, unsigned int, unsigned int, int) + 346
4   Chromium Framework                  0x00000001149f3e8f blink::WebGLRenderingContextBase::texImageByGPU(blink::WebGLRenderingContextBase::TexImageByGPUType, blink::WebGLTexture*, unsigned int, int, int, unsigned int, int, int, int, blink::CanvasImageSource*) + 591
5   Chromium Framework                  0x00000001149f44e7 blink::WebGLRenderingContextBase::texImageHelperHTMLCanvasElement(blink::WebGLRenderingContextBase::TexImageFunctionID, unsigned int, int, int, unsigned int, unsigned int, int, int, int, blink::HTMLCanvasElement*, blink::ExceptionState&) + 871
6   Chromium Framework                  0x00000001149f567f blink::WebGLRenderingContextBase::texSubImage2D(unsigned int, int, int, int, unsigned int, unsigned int, blink::HTMLCanvasElement*, blink::ExceptionState&) + 47
7   Chromium Framework                  0x0000000114ad2c01 blink::WebGLRenderingContextV8Internal::texSubImage2DMethodCallback(v8::FunctionCallbackInfo<v8::Value> const&) + 5153
8   Chromium Framework                  0x000000010eb0b957 v8::internal::FunctionCallbackArguments::Call(void (*)(v8::FunctionCallbackInfo<v8::Value> const&)) + 359
9   Chromium Framework                  0x000000010ebc62d8 v8::internal::MaybeHandle<v8::internal::Object> v8::internal::(anonymous namespace)::HandleApiCallHelper<false>(v8::internal::Isolate*, v8::internal::Handle<v8::internal::HeapObject>, v8::internal::Handle<v8::internal::HeapObject>, v8::internal::Handle<v8::internal::FunctionTemplateInfo>, v8::internal::Handle<v8::internal::Object>, v8::internal::BuiltinArguments) + 1016
10  Chromium Framework                  0x000000010ebc50ea v8::internal::Builtin_Impl_HandleApiCall(v8::internal::BuiltinArguments, v8::internal::Isolate*) + 330
11  Chromium Framework                  0x000000010ebc4eb1 v8::internal::Builtin_HandleApiCall(int, v8::internal::Object**, v8::internal::Isolate*) + 193
12  ???                                 0x000015fdd71063a7 0x0 + 24179979084711

Suspecting https://chromium.googlesource.com/chromium/src/+/33f717b1e3bf71f5001e08040a17024a9c6fa1b0 since it changes the files that appear in the stack trace.

zmo@ can you take a look?
 

Comment 1 by zmo@chromium.org, Aug 25 2016

Owner: kbr@chromium.org
I suggest not to do anything here since we are doing a major refactoring for the GPU-GPU copying path and that will definitely change the scenes to this crash.

By the way, this is a long time flakiness, not introduced by anything recently.

Comment 2 by kbr@chromium.org, Aug 25 2016

Blockedon: 612542
Components: -Internals>GPU>WebGL Blink>WebGL

Sign in to add a comment