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

Issue 730181 link

Starred by 1 user

Issue metadata

Status: WontFix
Owner: ----
Closed: Jun 2017
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug



Sign in to add a comment

GPU crashes on Nexus 7 opening websites with shaders

Project Member Reported by ssid@chromium.org, Jun 6 2017

Issue description

1. Open Chrome stable on Nexus 7 tablet.
2. Open shadertoy.com
3. Wait for a minute for GPU to crash.

The shaders never finish loading.

The logcat and symbolized minidump files are attached
stack trace:
 0  libchrome.so!gpu::GpuWatchdogThread::DeliberatelyTerminateToRecoverFromHang() [gpu_watchdog_thread.cc : 377 + 0x2]

 1  libchrome.so!base::debug::TaskAnnotator::RunTask(char const*, base::PendingTask*) [callback.h : 68 + 0x3]

 2  libchrome.so!base::MessageLoop::RunTask(base::PendingTask*) [message_loop.cc : 423 + 0xd]

 3  libchrome.so!base::MessageLoop::DeferOrRunPendingTask(base::PendingTask) [message_loop.cc : 434 + 0x7]

 4  libchrome.so!base::MessageLoop::DoDelayedWork(base::TimeTicks*) [message_loop.cc : 566 + 0x7]

 5  libchrome.so!base::MessagePumpDefault::Run(base::MessagePump::Delegate*) [message_pump_default.cc : 37 + 0x9]


 
logcat1
89.8 KB View Download
minidump1.dump
9.5 KB Download

Comment 1 by kbr@chromium.org, Jun 6 2017

Status: WontFix (was: Untriaged)
This is as expected. There are some shaders which take so long to compile that they trip the GPU watchdog. This is especially true on ShaderToy which does raymarching with lots of iterations. Don't worry about these, but try others.

Sign in to add a comment