GPU info collection crashes on Android due to assertion in v8 intl-objects.cc |
||||
Issue descriptionThe gpu_process_launch_tests, hardware_accelerated_feature_tests, and info_collection_tests are failing on all of the Android release bots. Example failure: https://build.chromium.org/p/chromium.gpu.fyi/builders/Android%20Release%20%28Nexus%209%29/builds/6287 The failure appears to be from an assertion failure: Fatal error in ../../v8/src/objects/intl-objects.cc, line 181 Check failed: canonical_time_zone != icu::UnicodeString(1, (const UChar *)u"Etc/GMT", -1). This appears to be from a v8 roll: https://codereview.chromium.org/2859273003 Which contains this commit: https://chromium-review.googlesource.com/496406
,
May 8 2017
,
May 8 2017
Thank you for the report. Do you know where the test in question is ? I failed to find it with CS.
,
May 8 2017
Issue 719707 has been merged into this issue.
,
May 8 2017
You need to build chrome, and then python content/test/gpu/run_gpu_integration_test.py info_collection --browser=android-chromium to reproduce. The test itself is in content/test/gpu/gpu_tests/
,
May 8 2017
If it's not a quick fix, can we revert the offending CL first so it can be included in the next V8 roll? After that, you can take the time to reproduce and investigate for a proper solution. Having multiple bots red is dangerous - demons might sneak in silently.
,
May 9 2017
Ok. I'll revert for now. Thank you for the pointer to the test.
,
May 9 2017
,
May 9 2017
The following revision refers to this bug: https://chromium.googlesource.com/v8/v8.git/+/f64f98460301bc349511b32637ada8bd2d7e0567 commit f64f98460301bc349511b32637ada8bd2d7e0567 Author: jshin <jshin@chromium.org> Date: Tue May 09 10:42:03 2017 Work around for crbug.com/719609 Temporarily disable check for Etc/GMT and take it as well as Etc/UTC until the root cause of crbug.com/719609 is found. BUG= chromium:719609 , v8:6252 TBR=adamk@chromium.org Review-Url: https://codereview.chromium.org/2872873002 Cr-Commit-Position: refs/heads/master@{#45186} [modify] https://crrev.com/f64f98460301bc349511b32637ada8bd2d7e0567/src/objects/intl-objects.cc
,
Aug 2
Etc/GMT is likely to come from Etc/Greenwich, Etc/GMT+0, Etc/GMT-0, Etc/GMT0. Anyway, this issue can be closed because DCHECK() turned out to be invalid anyway. That is, a CL recorded in comment 9 is not a work around but a real fix :-) |
||||
►
Sign in to add a comment |
||||
Comment 1 by geoffl...@chromium.org
, May 8 2017