Chrome crashing or hanging in PFQ informational builders
Reported by
jrbarnette@chromium.org,
Oct 26 2017
|
|||||
Issue description
All of the most recent chrome-pfq informational builders are failing:
https://uberchromegw.corp.google.com/i/chromeos.chrome/builders/tricky-tot-chrome-pfq-informational/builds/6553
https://uberchromegw.corp.google.com/i/chromeos.chrome/builders/peach_pit-tot-chrome-pfq-informational/builds/8300
https://uberchromegw.corp.google.com/i/chromeos.chrome/builders/caroline-tot-chrome-pfq-informational/builds/128
https://uberchromegw.corp.google.com/i/chromeos.chrome/builders/veyron_minnie-tot-chrome-pfq-informational/builds/6414
In all cases, the symptom is that after installing the new
build on hardware, the following message (or equivalent) is
reported at reboot:
After update and reboot, Chrome failed to reach login screen within 180 seconds
This message indicates a Chrome hang or crash at boot.
Because of bug 777969 , some peach_pit DUTs have been reporting this
message instead:
Chrome failed to reach login. System services not running.
This message is equivalent to the first message above.
The builds above are the first to show the symptom. We can expect
that when the current Chrome hits the PFQ, it will block uprev, so
this bug is a stopper.
,
Oct 26 2017
PFQ builders also started failing with similar error messages, as predicted by jrbarnette@. Master: https://uberchromegw.corp.google.com/i/chromeos/builders/master-chromium-pfq/builds/5057 Each board: https://luci-milo.appspot.com/buildbot/chromeos/veyron_minnie-chrome-pfq/1837 https://luci-milo.appspot.com/buildbot/chromeos/peach_pit-chrome-pfq/4199 https://luci-milo.appspot.com/buildbot/chromeos/reef-chrome-pfq/1141 https://luci-milo.appspot.com/buildbot/chromeos/tricky-chrome-pfq/4018 https://luci-milo.appspot.com/buildbot/chromeos/lumpy-chrome-pfq/10783 https://luci-milo.appspot.com/buildbot/chromeos/cyan-chrome-pfq/1836 https://luci-milo.appspot.com/buildbot/chromeos/betty-chrome-pfq/351 https://luci-milo.appspot.com/buildbot/chromeos/peppy-chrome-pfq/4190 https://luci-milo.appspot.com/buildbot/chromeos/amd64-generic-chromium-pfq/10782
,
Oct 26 2017
Chrome log left in ui.LATEST. (https://pantheon.corp.google.com/storage/browser/chromeos-autotest-results/151599158-chromeos-test/chromeos4-row9-rack9-host5/crashinfo.chromeos4-row9-rack9-host5/var/log/ui/) /opt/google/chrome/chrome: symbol lookup error: /usr/lib/libgestures.so.0: undefined symbol: gestures_log /opt/google/chrome/chrome: symbol lookup error: /usr/lib/libgestures.so.0: undefined symbol: gestures_log /opt/google/chrome/chrome: symbol lookup error: /usr/lib/libgestures.so.0: undefined symbol: gestures_log /opt/google/chrome/chrome: symbol lookup error: /usr/lib/libgestures.so.0: undefined symbol: gestures_log
,
Oct 26 2017
Did bisect with a kevin: 83365024efd81b5f3439d95c5560465ad2110388 is the first bad commit | commit 83365024efd81b5f3439d95c5560465ad2110388 Author: Tom Anderson <thomasanderson@chromium.org> Date: Wed Oct 25 18:24:47 2017 +0000 [Linux build] Add a linker version script to prevent symbol leaks Bug 770264 was caused by accidentally leaking FreeType symbols from Chrome. This CL adds a linker version script to ensure new leaks do not happen. Any newly exported symbols must be explicitly added to the version script. BUG=770264 R=thestig@chromium.org CC=pcc@chromium.org Change-Id: I4241bd836c1d0b9a0a05c80daa66a9823bcd52d8 Reviewed-on: https://chromium-review.googlesource.com/736834 Commit-Queue: Thomas Anderson <thomasanderson@chromium.org> Reviewed-by: Lei Zhang <thestig@chromium.org> Cr-Commit-Position: refs/heads/master@{#511522}
,
Oct 26 2017
Reverted the CL: https://chromium-review.googlesource.com/c/chromium/src/+/739261
,
Oct 27 2017
Finally got a green bulid on master-chromium-pfq. https://uberchromegw.corp.google.com/i/chromeos/builders/master-chromium-pfq/builds/5062
,
Jan 22 2018
,
Jan 23 2018
|
|||||
►
Sign in to add a comment |
|||||
Comment 1 by jrbarnette@chromium.org
, Oct 26 2017