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

Issue 652648 link

Starred by 2 users

Issue metadata

Status: Duplicate
Owner:
Closed: Oct 2016
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 2
Type: Bug



Sign in to add a comment

Chromebook crashes after suspend/resume

Project Member Reported by trevorbunker@google.com, Oct 4 2016

Issue description

UserAgent: Mozilla/5.0 (X11; CrOS x86_64 8743.44.0) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/54.0.2840.43 Safari/537.36
Platform: 8743.44.0 (Official Build) beta-channel samus

Steps to reproduce the problem:
1. Close lid to suspend
2. Wait some time
3. Open lid

What is the expected behavior?
Login to @google.com account and I'm still logged into my personal account, tabs are all set

What went wrong?
My machine had crashes, logged me out of both accounts, and when I did log back in, I needed to restore my tabs.

Crashed report ID: 0221a34300000000

How much crashed? Whole browser

Is it a problem with a plugin? N/A 

Did this work before? Yes ~ Oct 1

Chrome version: 54.0.2840.43  Channel: beta
OS Version: 8743.44.0
Flash Version: Shockwave Flash 23.0 r0
 
Project Member

Comment 1 by sheriffbot@chromium.org, Oct 4 2016

Labels: Hotlist-Google
Components: Services>Sync
Thread 0 CRASHED [SIGSEGV @ 0xffffebe65a568800 ] MAGIC SIGNATURE THREAD
0x00007f95c0d61d2f	(chrome -pref_change_registrar.cc:54 )	PrefChangeRegistrar::RemoveAll
0x00007f95c0d61d9a	(chrome -pref_change_registrar.cc:18 )	PrefChangeRegistrar::~PrefChangeRegistrar
0x00007f95c1ef7ab1	(chrome -typed_url_data_type_controller.cc:125 )	browser_sync::TypedUrlDataTypeController::~TypedUrlDataTypeController
0x00007f95c1ef7ad0	(chrome -typed_url_data_type_controller.cc:125 )	browser_sync::TypedUrlDataTypeController::~TypedUrlDataTypeController
0x00007f95c13d4e28	(chrome -ref_counted_delete_on_message_loop.h:62 )	base::RefCountedDeleteOnMessageLoop<sync_driver::DataTypeController>::Release
0x00007f95c13d4ea4	(chrome -ref_counted.h:407 )	base::internal::BindState<void (sync_driver::NonUIDataTypeController::*)(sync_driver::DataTypeController::ConfigureResult, const syncer::SyncMergeResult&, const syncer::SyncMergeResult&), scoped_refptr<sync_driver::NonUIDataTypeController> >::Destroy
0x00007f95c13d381d	(chrome -callback_internal.h:109 )	base::internal::BindState<base::Callback<void(sync_driver::DataTypeController::ConfigureResult, const syncer::SyncMergeResult&, const syncer::SyncMergeResult&), (base::internal::CopyMode)1>, sync_driver::DataTypeController::ConfigureResult, syncer::SyncMergeResult, syncer::SyncMergeResult>::Destroy
0x00007f95befb5544	(chrome -callback_internal.h:109 )	base::PendingTask::~PendingTask
0x00007f95c0915027	(chrome -message_loop.cc:525 )	base::MessageLoop::DeletePendingTasks
0x00007f95c091522c	(chrome -message_loop.cc:167 )	base::MessageLoop::~MessageLoop
0x00007f95bf45de0a	(chrome -message_loop.h:595 )	base::MessageLoopForUI::~MessageLoopForUI
0x00007f95bf462da0	(chrome -browser_main_loop.cc:421 )	content::BrowserMainLoop::~BrowserMainLoop
0x00007f95bf462ed9	(chrome -unique_ptr.h:76 )	content::BrowserMainRunnerImpl::Shutdown
0x00007f95bf45db48	(chrome -browser_main.cc:48 )	content::BrowserMain
0x00007f95c05be1a0	(chrome -content_main_runner.cc:786 )	content::ContentMainRunnerImpl::Run
0x00007f95c05bcd1a	(chrome -content_main.cc:20 )	content::ContentMain
0x00007f95bf25b521	(chrome -chrome_main.cc:85 )	ChromeMain
0x00007f95bc8ccfb5	(libc-2.19.so -libc-start.c:292 )	__libc_start_main
0x00007f95bf25b35d	(chrome + 0x0119235d )	_start
Components: OS>Kernel>Power
Owner: tbroch@chromium.org
Wasn't able to repro on latest beta build,

platform: 8743.54.0
chrome:   54.0.2840.49

But wasn't able to find anything particularly interesting in chrome diff here:

https://chromium.googlesource.com/chromium/src/+log/54.0.2840.43..54.0.2840.49?pretty=fuller&n=10000

to match SEGV

How frequently does the crash occur?

Going to try current version on beta channel ( 8743.44.0 ) as well.

Comment 4 by zea@chromium.org, Oct 4 2016

Cc: maxbogue@chromium.org
Max, didn't you investigate this issue recently, including some fixes to the DTC. Are those only in 55?
Yes, they were M55 only. The changes were too extensive for a merge to M54 to have been desirable.
Labels: -Pri-2 ReleaseBlock-Beta M-54 Pri-1
Status: Assigned (was: Unconfirmed)
are we reverting any changes to fix this?

Comment 8 by derat@chromium.org, Oct 5 2016

If one of the two bugs mentioned in #6 fixed this, please mark this bug as a duplicate and track any merge requests there.
Labels: -Pri-1 Pri-2
Mergedinto: 634088
Status: Duplicate (was: Assigned)
As I said in 634088, these crashes are not regressions and we will not be merging the fix back to M54.

Sign in to add a comment