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

Issue 600991 link

Starred by 2 users
Status: Duplicate
Merged: issue 594190
Owner: ----
Closed: Apr 2016
Cc:
ajha@chromium.org
█ kavvaru@chromium.org
pucchakayala@chromium.org
█ brajkumar@chromium.org
songsuk@chromium.org
█ durga.behera@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 1
Type: Bug-Regression



Sign in to add a comment

[Regression]:Chrome crashes on adding one account to another in Chrome os

Project Member Reported by sc00335...@techmahindra.com, Apr 6 2016 
Version: 51.0.2699.0/8155.0.0 (Official Build) dev-channel peppy,daisy,quawks
OS: Chrome os

What steps will reproduce the problem?
(1) Make sure you have 2 accounts. Say Person1 as parent account[Which can't be removed from system] and second account as Person2
(2) Sign out of all accounts >> Sign in to Person2 >> Open browser >> Click on uber tray options and click on profile name of person2 and click "Sign in another user.." 
(3) Now sign in to parent user[here Person1] by providing valid credentials and observe

Expected: No browser crash bubble should be seen and should be able to type in omnibox for some time

Actual:Instead browser crashes and unable to type anything in omnibox for sometime

This is a regression issue as no crash is seen in 50.0.2661.57/7978.36.0 beta channel daisy

No crash ids are seen.

Comment 1 by sc00335...@techmahindra.com, Apr 6 2016 

Attaching screenshot for reference.
Actual.png
270 KB View Download

Comment 2 by kavvaru@chromium.org, Apr 6 2016

Cc: songsuk@chromium.org pucchakayala@chromium.org
Labels: ReleaseBlock-Stable
Status: Untriaged (was: Unconfirmed)
Able to reproduce the issue on Peppy using chrome version 51.0.2699.0/8155.0.0.

Adding Stable blocker,Please feel free to remove if not required.

Thanks,

Comment 3 by sc00335...@techmahindra.com, Apr 6 2016 

NOTE: No crash id's are seen even after 1 hour.

Comment 4 by pucchakayala@chromium.org, Apr 6 2016

Labels: Needs-Feedback
Please open the terminal by pressing CTRL+ALT+T and run upload_crashes.
Check chrome://crashes for crash ID.

Comment 5 by sc00335...@techmahindra.com, Apr 7 2016

Labels: -Needs-Feedback
Crash id's: e70c9a8400000000 , 98549a8400000000 , 31db1a8400000000

Comment 6 by kavvaru@chromium.org, Apr 7 2016 

Stack trace of the report id 
=====================
Thread 0 CRASHED [SIGSEGV @ 0x00000038 ] MAGIC SIGNATURE THREAD
0x00007f478d2f0510	(chrome + 0x02940510 )	
0x00007f478d575889	(chrome + 0x02bc5889 )	
0x00007f478d5705da	(chrome + 0x02bc05da )	
0x00007f478d571bdf	(chrome + 0x02bc1bdf )	
0x00007f478d5756da	(chrome + 0x02bc56da )	
0x00007f478d575c53	(chrome + 0x02bc5c53 )	
0x00007f478d5761d8	(chrome + 0x02bc61d8 )	
0x00007f478a9dcd02	(chrome + 0x0002cd02 )	
0x00007f478a31b618	(chrome -callback.h:397 )	base::debug::TaskAnnotator::RunTask
0x00007f478a31a785	(chrome -message_loop.cc:476 )	base::MessageLoop::DoWork
0x00007f478a502b12	(chrome -message_pump_libevent.cc:229 )	base::MessagePumpLibevent::Run
0x00007f478ad53708	(chrome + 0x003a3708 )	
0x00007f478df26824	(chrome + 0x03576824 )	
0x00007f478cd9b20a	(chrome + 0x023eb20a )	
0x00007f478cbe5a14	(chrome + 0x02235a14 )	
0x00007f478cbe58f2	(chrome + 0x022358f2 )	
0x00007f478ad07c51	(chrome + 0x00357c51 )	
0x00007f478ad0690a	(chrome + 0x0035690a )	
0x00007f478a9b047e	(chrome + 0x0000047e )	
0x00007f4788839fb5	(libc-2.19.so -libc-start.c:292 )	__libc_start_main
0x00007f478a1f7268	(chrome + 0x00005268 )	_init
0x00007ffeb9c988d7

Comment 7 by frankt3...@gmail.com, Apr 8 2016 

#CBC-RS/TC-watchlist

Comment 8 by rookrishna@chromium.org, Apr 11 2016

Mergedinto: 594190
Status: Duplicate (was: Untriaged)
►

Sign in to add a comment