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

Issue 768326 link

Starred by 5 users

Issue metadata

Status: Verified
Owner:
Last visit 16 days ago
Closed: Oct 2017
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 1
Type: Bug-Regression



Sign in to add a comment

Regression:Chrome crash is seen on each sign-out from Uber tray in ARC devices.

Project Member Reported by jbanavatu@chromium.org, Sep 25 2017

Issue description

Chrome Version:  63.0.3222.0/9972.0.0 dev-channel Reks
OS: Chrome OS

What steps will reproduce the problem?
(1)Sign in to chrome with valid credentials >> Open Uber tray >> Click on sign out button and Observe

Expected: No crash should be seen on signing out.
Actual: Instead,Chrome crash is seen on each sign-out from Uber tray.

This is regression issue as no crash is seen in 61.0.3163.101/9765.70.0 beta channel reks.

Crash id's: 72329b9f834b85d6,d1a74f23fcb8d916

Stack trace: 
Thread 0 (id: 17) CRASHED [SIGABRT @ 0x00000000 ]
Stack Quality100%Show frame trust levels
0xee27fa30	(linux-gate.so + 0x00000a30 )	__kernel_vsyscall
0xee051a2c	(libc.so + 0x0008aa2c )	tgkill
0xee04d285	(libc.so -pthread_kill.cpp:45 )	pthread_kill
0xedffdcfa	(libc.so -raise.cpp:34 )	raise
0xedff5246	(libc.so -abort.cpp:47 )	abort
0xee0f77c1	(libbase.so -logging.cpp:404 )	android::base::LogMessage::~LogMessage()
0x5e87adc2	(tzdatacheck -tzdatacheck.cpp:57 )	readHeader(std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> > const&, char*, unsigned int)
0x5e879fe6	(tzdatacheck -tzdatacheck.cpp:191 )	main
0xedfdc35c	(libc.so -libc_init_dynamic.cpp:109 )	__libc_init
0x5e879d22	(tzdatacheck + 0x00000d22 )	_start

Note: This crash is seen only in ARC devices.


 

Comment 1 by gkihumba@google.com, Sep 25 2017

Reluctant to block dev on this, will make it beta blocker.

Comment 2 by gkihumba@google.com, Sep 25 2017

Labels: -ReleaseBlock-Dev ReleaseBlock-Beta

Comment 3 by gkihumba@google.com, Oct 16 2017

Owner: jbanavatu@chromium.org
Status: Assigned (was: Untriaged)
Is this still seen?
Owner: mmanchala@chromium.org
Assigning it to Manisha as jbanavatu@ is OOO.
Owner: tbuck...@chromium.org
Checked Issue on latest ToT build 64.0.3241.0/10041.0.0 dev-channel Reks.
Able to repro the issue i.e. Chrome crash is seen on sign-out from Uber tray.

Attaching Crash Ids:
eb7dba0ae37834c7
555ec4cac4f0e849

@tbuckley : Please confirm the issue
Owner: shihuis@google.com
This sounds more ARC-related than system-menu. @shihuis can someone on ARC look into this crash?

Comment 7 by gkihumba@google.com, Oct 25 2017

Owner: bhthompson@chromium.org
Owner: khmel@chromium.org
Yury, have you seen anything like this?

If not please feel free to pass it on.

Comment 9 by khmel@chromium.org, Oct 25 2017

Personally I saw a lot of crashes from "tzdatacheck", especially on Eve.

Comment 10 by khmel@chromium.org, Oct 27 2017

This happens on Android side, that is why it visible only on ARC devices.

Comment 12 by khmel@chromium.org, Oct 27 2017

Found in one bug report:

--------- beginning of system
10-23 18:08:37.793     6     6 I vold    : Vold 3.0 (the awakening) firing up
10-23 18:08:37.793     6     6 V vold    : Detected support for: ext4
10-23 18:08:38.075     6    16 D vold    : e4crypt_init_user0
10-23 18:08:38.075     6    16 D vold    : e4crypt_prepare_user_storage for volume null, user 0, serial 0, flags 1
10-23 18:08:38.075     6    16 D vold    : Preparing: /data/system/users/0
10-23 18:08:38.075     6    16 E cutils  : Failed to mkdir(/data/system/users/0): No such file or directory
10-23 18:08:38.075     6    16 E vold    : Failed to prepare /data/system/users/0: No such file or directory
10-23 18:08:38.075     6    16 E vold    : Failed to prepare user 0 storage
10-23 18:08:38.075     1     1 I vdc     : 400 7 Command failed
10-23 18:08:38.075     1     1 I vdc     : vdc terminated by exit(144)
10-23 18:08:38.102    17    17 F /system/bin/tzdatacheck: tzdatacheck.cpp:57] Error opening tzdata file /data/misc/zoneinfo/current/tzdata: Permission denied


Comment 13 by khmel@chromium.org, Oct 27 2017

Owner: lhchavez@chromium.org
Reassigning to Luis once he did some fixes in this field.
Labels: -ReleaseBlock-Beta ReleaseBlock-Stable
This seems to be a dup of  issue 741031 
Moving to stable blocker as this is in M61 too

Luis, any update on this one? 
Labels: M-61 Merge-Request-61
Status: Fixed (was: Assigned)
It was fixed in CrOS 10048.0.0 / Chrome 64.0.3244.0

Just flashed R64-10081.0.0 (Official Build) dev-channel veyron_minnie test and I see no more crashes:

localhost ~ # android-sh -c logcat | grep tzdata                                                                                                                                                                                                                               
10-31 19:56:53.750  2953  2953 W tzdatacheck: type=1400 audit(0.0:13): avc: denied { module_request } for kmod="personality-8" scontext=u:r:tzdatacheck:s0 tcontext=u:r:kernel:s0 tclass=system permissive=0
10-31 19:57:22.000  3406  3406 W tzdatacheck: type=1400 audit(0.0:23): avc: denied { module_request } for kmod="personality-8" scontext=u:r:tzdatacheck:s0 tcontext=u:r:kernel:s0 tclass=system permissive=0
10-31 19:58:09.730  4671  4671 W tzdatacheck: type=1400 audit(0.0:90): avc: denied { module_request } for kmod="personality-8" scontext=u:r:tzdatacheck:s0 tcontext=u:r:kernel:s0 tclass=system permissive=0
10-31 19:58:50.146    17    17 I /system/bin/tzdatacheck: tzdata file /data/misc/zoneinfo/current/tzdata does not exist. No action required.

I manually checked the crashes after the point in time where it was fixed (Chrome >= 64.0.3244.0)[1] and 100% of them come from a single user with a mismatching Chrome OS version, so it's most likely a developer.

Similarly, in R63 there have been zero crashes after R63-10032.8.0, and for R62 after R62-9901.54.0.

Re: 61, can I merge the fix to R61?

1: https://crash.corp.google.com/browse?q=product.Version%3E%3D%2764.0.3244.0%27%20AND%20product.name%3D%27ChromeOS_ARC%27%20OMIT%20RECORD%20IF%20SUM(CrashedStackTrace.StackFrame.FunctionName%3D%27readHeader(std%3A%3A__1%3A%3Abasic_string%3Cchar%2C%20std%3A%3A__1%3A%3Achar_traits%3Cchar%3E%2C%20std%3A%3A__1%3A%3Aallocator%3Cchar%3E%20%3E%20const%26%2C%20char*%2C%20unsigned%20int)%27)%20%3D%200&sql_dialect=dremelsql&ignore_case=false&enable_rewrite=true&omit_field_name=CrashedStackTrace.StackFrame.FunctionName&omit_field_value=readHeader(std%3A%3A__1%3A%3Abasic_string%3Cchar%2C%20std%3A%3A__1%3A%3Achar_traits%3Cchar%3E%2C%20std%3A%3A__1%3A%3Aallocator%3Cchar%3E%20%3E%20const%26%2C%20char*%2C%20unsigned%20int)&omit_field_opt=%3D
Labels: -M-61 -Merge-Request-61
Status: Verified (was: Fixed)
D'oh, R61 is retired now. Ignore the merge requests, marking this as verified since there are no more new crashes for a whole week!
Labels: Merge-TBD
[Auto-generated comment by a script] We noticed that this issue is targeted for M-63; it appears the fix may have landed after branch point, meaning a merge might be required. Please confirm if a merge is required here - if so add Merge-Request-63 label, otherwise remove Merge-TBD label. Thanks.
Labels: -Merge-TBD
removing merge request since the issue seems to be resolved in M63 and M62, please re add it if needed 

Sign in to add a comment