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

Issue 779207 link

Starred by 2 users

Issue metadata

Status: Duplicate
Owner:
Closed: Dec 2017
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 1
Type: Bug



Sign in to add a comment

login_CryptohomeLogin failure on various builders

Project Member Reported by jdufault@chromium.org, Oct 27 2017

Issue description

Example failure at [1]. I suspect this is a flake because this is the only bot that went red, but TBD after some additional runs. I looked in logs and it looks like cryptohomed is crashing.

  2017-10-27T18:52:28.033876+00:00 CRIT cryptohomed[1948]: Check failed: this == g_top_manager (0x7f09ac007e80 vs. 0x7f09be8b21e0)#012/usr/lib64/libbase-core-395517.so(base::debug::StackTrace::StackTrace()+0x13) [0x7f09bd6bfd43]#012

1: https://uberchromegw.corp.google.com/i/chromeos.chrome/builders/tricky-tot-chrome-pfq-informational/builds/6574
 
If this was not a flake then it will probably bring the PFQ down.
Failure looks like it was a flake.
Labels: -Pri-2 Pri-1
Seems to be a relatively common flake though [1]. Here is another failure.

  2017-10-26T22:23:09.489309+00:00 CRIT cryptohomed[1347]: Check failed: this == g_top_manager (0x7f398c033d60 vs. 0x7f399ea760a0)#012/usr/lib64/libbase-core-395517.so(base::debug::StackTrace::StackTrace()+0x13) [0x7f399cb39d43]#012

1: https://uberchromegw.corp.google.com/i/chromeos.chrome/builders/tricky-tot-chrome-pfq-informational/builds/6561
Cc: malaykeshav@chromium.org warx@chromium.org
Seen here too:
https://uberchromegw.corp.google.com/i/chromeos/builders/sentry-paladin/builds/1652
https://pantheon.corp.google.com/storage/browser/chromeos-autotest-results/159131931-chromeos-test/chromeos4-row8-rack9-host5/cheets_StartAndroid.stress/sysinfo/var/log/

Looking at messages:
2017-11-29T01:07:22.188339+00:00 CRIT cryptohomed[1487]: Check failed: this == g_top_manager (0x72a13c009de0 vs. 0x6092da6f7710)#012/usr/lib64/libbase-core-
...
2017-11-29T01:07:22.217942+00:00 WARNING crash_reporter[4187]: [user] Received crash notification for cryptohomed[1487] sig 6, user 0 (developer build - not testing - always dumping)

I don't think this is what ends up causing the test to fail though.

crashdump attached.
159131931-chromeos-test%2Fchromeos4-row8-rack9-host5%2Fdebug%2Fcryptohomed.20171128.170722.1487.dmp.txt
32.5 KB View Download
Cc: slavamn@chromium.org xixuan@chromium.org athilenius@chromium.org
Summary: login_CryptohomeLogin failure on various builders (was: login_CryptohomeLogin failure on tricky-tot-chrome-pfq-informational)
Seen here again:
https://luci-milo.appspot.com/buildbot/chromeos/lumpy-paladin/30367
https://pantheon.corp.google.com/storage/browser/chromeos-autotest-results/159213667-chromeos-test/chromeos6-row2-rack7-host19/security_ProfilePermissions.login/sysinfo/

2017-11-29T08:30:58.142612+00:00 CRIT cryptohomed[1139]: Check failed: this == g_top_manager (0x7f4a54001740 vs. 0x7f4a64108c50)#012/usr/lib64/libbase-core-395517.so(base::debug::StackTrace::StackTrace()+0x13) [0x7f4a6275bfd3]#012
b/69871115#comment4 (cheets_StartAndroid.stress failure) also has:

2017-11-29T01:07:22.188339+00:00 CRIT cryptohomed[1487]: Check failed: this == g_top_manager (0x72a13c009de0 vs. 0x6092da6f7710)#012/usr/lib64/libbase-core-395517.so(base::debug::StackTrace::StackTrace()+0x13) [0x72a14b3b6dc3]#012

Cc: ejcaruso@chromium.org
See also analysis in http://b/69871115 (comments 7-11).
Components: UI>Shell>LockScreen
Status: Started (was: Assigned)
Minimal CL to deal with crashes is submitted for review - see http://b/69871115#comment20.
Mergedinto: 794375
Status: Duplicate (was: Started)
Mergedinto: -794375 794403
A better duplicate...

Sign in to add a comment