android gpu hangs on old devices |
||||||
Issue descriptionThis is m63 and after, because m62 is dominated by crbug.com/772049 Picking 63.0.3239.53: https://crash.corp.google.com/browse?q=product.name%3D%27Chrome_Android%27%20AND%20product.Version%3D%2763.0.3239.53%27%20OMIT%20RECORD%20IF%20SUM(CrashedStackTrace.StackFrame.FunctionName%3D%27gpu%3A%3AGpuWatchdogThread%3A%3ADeliberatelyTerminateToRecoverFromHang()%27)%20%3D%200&sql_dialect=dremelsql&ignore_case=false&enable_rewrite=true&omit_field_name=CrashedStackTrace.StackFrame.FunctionName&omit_field_value=gpu%3A%3AGpuWatchdogThread%3A%3ADeliberatelyTerminateToRecoverFromHang()&omit_field_opt=%3D#-processtype,-channel,-magicsignature:50,+operatingsystem,-systemmodified,-country,-magicsignaturesorted This is the distribution: 1 Android Jelly Bean 30.10% 692 2 Android KitKat 29.27% 673 3 Android Marshmallow 21.75% 500 4 Android Lollipop 16.18% 372 5 Android Nougat 1.44% 33 6 Android O 0.87% 20 7 Android ??? 0.30% 7 8 Android Ice Cream Sandwich 0.09% 2 And compare that to android distribution: https://developer.android.com/about/dashboards/index.html 4.1.x Jelly Bean 16 2.2% 4.2.x 17 3.1% 4.3 18 0.9% 4.4 KitKat 19 13.8% 5.0 Lollipop 21 6.4% 5.1 22 20.8% 6.0 Marshmallow 23 30.9% 7.0 Nougat 24 17.6% 7.1 25 3.0% 8.0 Oreo 26 0.3% JB and KK is definitely over represented. Suspicion is that these are just slower devices, but who knows, might be worth looking into. Or wait long enough and JB support will be dropped.. Filing tracking bug so individual bugs/signatures can be merged here
,
Nov 28 2017
Issue 785510 has been merged into this issue.
,
Nov 28 2017
Issue 786383 has been merged into this issue.
,
Nov 29 2017
Issue 760060 has been merged into this issue.
,
Dec 13 2017
Issue 760575 has been merged into this issue.
,
Jan 18 2018
Users experienced this crash on the following builds: Android Dev 65.0.3316.0 - 0.82 CPM, 36 reports, 35 clients (signature [GPU hang] re2::DFA::AnalyzeSearchHelper) If this update was incorrect, please add "Fracas-Wrong" label to prevent future updates. - Go/Fracas
,
Jan 22 2018
Users experienced this crash on the following builds: Android Beta 64.0.3282.99 - 0.27 CPM, 22 reports, 16 clients (signature [GPU hang] gpu::gles2::GLES2Util::GetStringEnum) If this update was incorrect, please add "Fracas-Wrong" label to prevent future updates. - Go/Fracas
,
Feb 18 2018
Users experienced this crash on the following builds: Android Dev 66.0.3348.3 - 0.38 CPM, 4 reports, 3 clients (signature [GPU hang] base::CommandLine::HasSwitch) If this update was incorrect, please add "Fracas-Wrong" label to prevent future updates. - Go/Fracas
,
Mar 9 2018
Issue 820352 has been merged into this issue.
,
Mar 13 2018
Users experienced this crash on the following builds: Android Beta 65.0.3325.144 - 0.17 CPM, 25 reports, 22 clients (signature [GPU hang] gpu::gles2::ErrorStateImpl::~ErrorStateImpl) If this update was incorrect, please add "Fracas-Wrong" label to prevent future updates. - Go/Fracas
,
Mar 23 2018
Users experienced this crash on the following builds: Mac Canary 67.0.3378.0 - 0.22 CPM, 1 reports, 1 clients (signature [GPU hang] gpu::gles2::ErrorStateImpl::CopyRealGLErrorsToWrapper) If this update was incorrect, please add "Fracas-Wrong" label to prevent future updates. - Go/Fracas
,
May 14 2018
Issue 839587 has been merged into this issue. |
||||||
►
Sign in to add a comment |
||||||
Comment 1 by boliu@chromium.org
, Nov 28 2017