Roaming profile data and syncing via google does not work or crashes chrome
Reported by
thea.s.b...@gmail.com,
Sep 6 2017
|
|||||
Issue descriptionUserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/60.0.3112.113 Safari/537.36 Steps to reproduce the problem: 1.Enable the creation of roaming copies for Google Chrome profile data (group policy) 2. Sign in to google services for sync. 3. Sync does not work (does not sync) or: 1. Sign in to google services for sync. 2. Enable the creation of roaming copies for Google Chrome profile data(group policy) 3. Reopen Chrome 4. Chrome crashes on startup until "Sync data" folder is deleted 5. Chrome does not sync What is the expected behavior? Chrome syncs the users settings from Google services and roames them via roaming profile data folder. What went wrong? If sync was enabled before "Enable the creation of roaming copies for Google Chrome profile data" was enabled, Chrome crashes on startup until deleting the "Sync data"-folder. Then it still does not sync from google, but stops crashing. If sync was enabled after the "Enable the creation of roaming copies for Google Chrome profile data" was enabled, it just does not sync from google. Did this work before? N/A Chrome version: 60.0.3112.113 Channel: stable OS Version: 2016 Flash Version: Reproduced on 61.0.3163.79 also
,
Sep 7 2017
ID-en for den opplastede programstopprapporten: cc1ac6c1e5070abe (lokal kræsj-ID: 09869e5c-0900-43d6-816e-a9bf1903ab87)
,
Sep 7 2017
Thanks for providing the details, but the crash id provided seems to have no data in crash server. It shows as the crash ID is either not processed yet or it has expired. Request you to please provide any other crash ID if generated. Looping enterprise team incase they can provide any help. Thanks!
,
Sep 7 2017
ID-en for den opplastede programstopprapporten: efd630a8f870a252 (lokal kræsj-ID: 0f478c97-d9f1-4c1a-9637-5966ceae3421) Its from just now (two minutes ago) Any earlier was not uploaded / is not uploaded yet since automatic uploading was not enabled.
,
Sep 7 2017
Thank you for providing more feedback. Adding requester "ranjitkan@chromium.org" to the cc list and removing "Needs-Feedback" label. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Sep 7 2017
Thanks for the crash id. Crash Report - go/crash/efd630a8f870a252 ============= Thread 0 (id: 8824) CRASHED [EXCEPTION_ACCESS_VIOLATION_READ @ 0x00000008 ] MAGIC SIGNATURE THREAD Stack Quality90%Show frame trust levels 0x00007ffe9a70c407 (chrome.dll -profile_sync_service.cc:1148 ) browser_sync::ProfileSyncService::OnActionableError(syncer::SyncProtocolError const &) 0x00007ffe9a9596ac (chrome.dll -bind_internal.h:329 ) base::internal::Invoker<base::internal::BindState<void ( syncer::SyncBackendHostImpl::*)(syncer::SyncProtocolError const &),base::WeakPtr<syncer::SyncBackendHostImpl>,syncer::SyncProtocolError>,void >::Run(base::internal::BindStateBase *) 0x00007ffe98fa1de1 (chrome.dll -task_annotator.cc:59 ) base::debug::TaskAnnotator::RunTask(char const *,base::PendingTask *) 0x00007ffe98f44485 (chrome.dll -message_loop.cc:422 ) base::MessageLoop::RunTask(base::PendingTask *) 0x00007ffe98f44fe2 (chrome.dll -message_loop.cc:540 ) base::MessageLoop::DoWork() 0x00007ffe98fa2360 (chrome.dll -message_pump_win.cc:173 ) base::MessagePumpForUI::DoRunLoop() 0x00007ffe98fa1fe3 (chrome.dll -message_pump_win.cc:56 ) base::MessagePumpWin::Run(base::MessagePump::Delegate *) 0x00007ffe98f74938 (chrome.dll -run_loop.cc:111 ) base::RunLoop::Run() 0x00007ffe98e812a3 (chrome.dll -chrome_browser_main.cc:1967 ) ChromeBrowserMainParts::MainMessageLoopRun(int *) 0x00007ffe988570bb (chrome.dll -browser_main_runner.cc:142 ) content::BrowserMainRunnerImpl::Run() 0x00007ffe9884fd04 (chrome.dll -browser_main.cc:46 ) content::BrowserMain(content::MainFunctionParams const &) 0x00007ffe98dd3c66 (chrome.dll -content_main_runner.cc:686 ) content::ContentMainRunnerImpl::Run() 0x00007ffe98defd3d (chrome.dll -main.cc:469 ) service_manager::Main(service_manager::MainParams const &) 0x00007ffe98dd358b (chrome.dll -content_main.cc:19 ) content::ContentMain(content::ContentMainParams const &) 0x00007ffe984fdd51 (chrome.dll -chrome_main.cc:139 ) ChromeMain 0x00007ff62a2375ae (chrome.exe -main_dll_loader_win.cc:199 ) MainDllLoader::Launch(HINSTANCE__ *,base::TimeTicks) 0x00007ff62a2325f2 (chrome.exe -chrome_exe_main_win.cc:266 ) wWinMain 0x00007ff62a2ea052 (chrome.exe -exe_common.inl:253 ) __scrt_common_main_seh 0x00007ffed41d8363 (KERNEL32.DLL + 0x00008363 ) BaseThreadInitThunk 0x00007ffed6567090 (ntdll.dll + 0x00067090 ) 0x00007ffed33a4e1f (KERNELBASE.dll + 0x00054e1f ) This crash existed from M57 onwards. Below is the historical data. As of now only minor instances in latest M61 stable. 61.0.3163.79 0.43% 2 61.0.3160.0 0.22% 1 60.0.3112.113 8.41% 39 60.0.3112.101 10.56% 49 60.0.3112.90 3.88% 18 60.0.3112.78 3.66% 17 60.0.3088.0 0.43% 2 59.0.3071.115 18.53% 86 59.0.3071.109 0.86% 4 59.0.3071.86 2.16% 10 58.0.3029.110 29.31% 136 58.0.3029.96 3.45% 16 58.0.3029.83 4.09% 19 58.0.3029.81 6.68% 31 57.0.2987.133 6.25% 29 57.0.2987.132 0.22% 1 57.0.2987.110 0.22% 1 Link to the builds which introduced the crash =============================================== https://crash.corp.google.com/browse?q=custom_data.ChromeCrashProto.ptype%3D%27browser%27%20AND%20custom_data.ChromeCrashProto.magic_signature_1.name%3D%27browser_sync%3A%3AProfileSyncService%3A%3AOnActionableError%27&sql_dialect=dremelsql&ignore_case=false&enable_rewrite=true&omit_field_name=&omit_field_value=&omit_field_opt=%3D&unnest=#-property-selector,samplereports:5,+productversion:1000 Julian fixed a similar bug, Issue 687882 so assigning. Tagging for fix during M63 time frame.
,
Sep 21 2017
,
May 9 2018
Hi, How can I see the status on this? I am not allowed to view https://bugs.chromium.org/p/chromium/issues/detail?id=743592 |
|||||
►
Sign in to add a comment |
|||||
Comment 1 by ligim...@chromium.org
, Sep 6 2017Labels: Needs-Triage-M61