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

Issue 659144 link

Starred by 2 users

Issue metadata

Status: Duplicate
Merged: issue 659892
Owner:
Closed: Oct 2016
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 2
Type: Bug



Sign in to add a comment

WebGL2 conformance test buffers_one_large_uniform_buffer failing on Win8 Release (NVIDIA) fyi bot

Project Member Reported by ajuma@chromium.org, Oct 25 2016

Issue description

WebglConformance_conformance2_buffers_one_large_uniform_buffer started failing on the Win8 Release (NVIDIA) FYI bot at build https://build.chromium.org/p/chromium.gpu.fyi/builders/Win8%20Release%20%28NVIDIA%29/builds/24968

Crash stack:
	(No symbol) [0x6943D17E]
	(No symbol) [0x6937FDFC]
	gpu::gles2::BufferManager::DoBufferData [0x6C91E52A+203]
	gpu::gles2::BufferManager::ValidateAndDoBufferData [0x6C91F5E7+295]
	gpu::gles2::GLES2DecoderImpl::HandleBufferData [0x6CEF7013+82]
	gpu::gles2::GLES2DecoderImpl::DoCommandsImpl<0> [0x6CEE0174+204]
	gpu::CommandParser::ProcessCommands [0x6C92EE37+49]
	gpu::CommandExecutor::PutChanged [0x6CF0DE22+481]
	gpu::CommandBufferService::Flush [0x6CEDF28C+41]
	gpu::GpuCommandBufferStub::OnAsyncFlush [0x6C9E5B51+353]
	IPC::MessageT<GpuCommandBufferMsg_AsyncFlush_Meta,std::tuple<int,unsigned int,std::vector<ui::LatencyInfo,std::allocator<ui::LatencyInfo> > >,void>::Dispatch<gpu::GpuCommandBufferStub,gpu::GpuCommandBufferStub,void,void (__thiscall gpu::GpuCommandBufferSt [0x6C9E3B9D+142]
	gpu::GpuCommandBufferStub::OnMessageReceived [0x6C9E6453+485]
	gpu::GpuChannel::HandleMessageHelper [0x6C9DFE37+44]
	gpu::GpuChannel::HandleMessage [0x6C9DFD78+346]
	base::internal::InvokeHelper<1,void>::MakeItSo<void (__thiscall media::AudioRendererImpl::*const &)(media::PipelineStatistics const &),base::WeakPtr<media::AudioRendererImpl> const &,media::PipelineStatistics const &> [0x6B976F55+41]
	base::internal::Invoker<base::internal::BindState<void (__thiscall gpu::gles2::GLES2Implementation::*)(base::Callback<void __cdecl(void),1,1> const &),base::WeakPtr<gpu::gles2::GLES2Implementation>,base::Callback<void __cdecl(void),1,1> >,void __cdecl(voi [0x6B8451F8+23]

jmadill@, could this have been triggered by the ANGLE roll (https://chromium.googlesource.com/chromium/src/+/b95b6a4927ec8bb31a3aebcebbf7b5afc6c7d1b6)?
 
Cc: -zmo@chromium.org
Labels: -Pri-3 Pri-2
Owner: zmo@chromium.org
Status: Assigned (was: Available)
This actually started in https://build.chromium.org/p/chromium.gpu.fyi/builders/Win8%20Release%20%28NVIDIA%29/builds/24967

I see that https://codereview.chromium.org/2435803004 touches some files from this stack trace. zmo@, could you check this, please?

Comment 3 by zmo@chromium.org, Oct 26 2016

It's more likely https://codereview.chromium.org/2435803004, but I don't have a win8 bot to reproduce this.
You should be able to check it on the actual waterfall bot with "Chrome Internal GPU Pixel Wrangling Instructions"

Comment 6 by zmo@chromium.org, Oct 27 2016

Mergedinto: 659892
Status: Duplicate (was: Assigned)

Sign in to add a comment