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

Issue 871813 link

Starred by 4 users
Status: Fixed
Owner:
mamir@chromium.org
Closed: Aug 22
Cc:
█ abdulsyed@chromium.org
gov...@chromium.org
mac-bugs-priority@chromium.org
EstimatedDays: ----
NextAction: ----
OS: Mac
Pri: 0
Type: Bug



Sign in to add a comment

Canary Crashes at Start-Up and will not reload/re-open

Reported by jonathan.wolch@gmail.com, Aug 7 
UserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_13_6) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/67.0.3396.99 Safari/537.36

Steps to reproduce the problem:
1. LOAD CHROME!
2. 
3. 

What is the expected behavior?
It should open

What went wrong?
It refuses to load

Did this work before? N/A 

Chrome version: 67.0.3396.99  Channel: n/a
OS Version: OS X 10.13.6
Flash Version: 

Process:               Google Chrome Canary [1467]
Path:                  /Applications/Google Chrome Canary.app/Contents/MacOS/Google Chrome Canary
Identifier:            com.google.Chrome.canary
Version:               70.0.3515.0 (3515.0)
Code Type:             X86-64 (Native)
Parent Process:        ??? [1]
Responsible:           Google Chrome Canary [1467]
User ID:               501

Date/Time:             2018-08-07 12:19:15.946 -0400
OS Version:            Mac OS X 10.13.6 (17G65)
Report Version:        12
Anonymous UUID:        8C99E5CA-54BE-F191-F488-4DE84129FFF7

Time Awake Since Boot: 340 seconds

System Integrity Protection: enabled

Crashed Thread:        42  Chrome_SyncThread

Exception Type:        EXC_CRASH (SIGABRT)
Exception Codes:       0x0000000000000000, 0x0000000000000000

Application Specific Information:
terminating with uncaught exception of type std::out_of_range: basic_string
abort() called

Thread 0:: CrBrowserMain  Dispatch queue: com.apple.main-thread
0   com.google.Chrome.framework   	0x00000001064dca22 0x105b5a000 + 9972258
1   com.google.Chrome.framework   	0x00000001064dedde 0x105b5a000 + 9981406
2   com.google.Chrome.framework   	0x00000001064cd60f 0x105b5a000 + 9909775
3   com.google.Chrome.framework   	0x00000001064c3294 0x105b5a000 + 9867924
4   com.google.Chrome.framework   	0x0000000107fa642d 0x105b5a000 + 38061101
5   com.google.Chrome.framework   	0x0000000107f9880c 0x105b5a000 + 38004748
6   com.google.Chrome.framework   	0x0000000107f98ef1 0x105b5a000 + 38006513
7   com.google.Chrome.framework   	0x0000000107faca88 0x105b5a000 + 38087304
8   com.google.Chrome.framework   	0x0000000109444eda 0x105b5a000 + 59682522
9   com.google.Chrome.framework   	0x0000000107ea1212 0x105b5a000 + 36991506
10  com.google.Chrome.framework   	0x0000000107ebf39f 0x105b5a000 + 37114783
11  com.google.Chrome.framework   	0x0000000107ebf843 0x105b5a000 + 37115971
12  com.google.Chrome.framework   	0x0000000107ec20ba 0x105b5a000 + 37126330
13  com.google.Chrome.framework   	0x0000000107eb341a 0x105b5a000 + 37065754
14  com.google.Chrome.framework   	0x0000000107ec19df 0x105b5a000 + 37124575
15  com.apple.CoreFoundation      	0x00007fff2bd96d31 __CFRUNLOOP_IS_CALLING_OUT_TO_A_SOURCE0_PERFORM_FUNCTION__ + 17
16  com.apple.CoreFoundation      	0x00007fff2be4e60c __CFRunLoopDoSource0 + 108
17  com.apple.CoreFoundation      	0x00007fff2bd79ce0 __CFRunLoopDoSources0 + 208
18  com.apple.CoreFoundation      	0x00007fff2bd7915d __CFRunLoopRun + 1293
19  com.apple.CoreFoundation      	0x00007fff2bd789b7 CFRunLoopRunSpecific + 487
20  com.apple.HIToolbox           	0x00007fff2b058d96 RunCurrentEventLoopInMode + 286
21  com.apple.HIToolbox           	0x00007fff2b058b06 ReceiveNextEventCommon + 613
22  com.apple.HIToolbox           	0x00007fff2b058884 _BlockUntilNextEventMatchingListInModeWithFilter + 64
23  com.apple.AppKit              	0x00007fff29309a73 _DPSNextEvent + 2085
24  com.apple.AppKit              	0x00007fff29a9fe34 -[NSApplication(NSEvent) _nextEventMatchingEventMask:untilDate:inMode:dequeue:] + 3044
25  com.google.Chrome.framework   	0x0000000107ad92a0 0x105b5a000 + 33026720
26  com.google.Chrome.framework   	0x0000000107eb341a 0x105b5a000 + 37065754
27  com.google.Chrome.framework   	0x0000000107ad91d4 0x105b5a000 + 33026516
28  com.apple.AppKit              	0x00007fff292fe885 -[NSApplication run] + 764
29  com.google.Chrome.framework   	0x0000000107ec297c 0x105b5a000 + 37128572
30  com.google.Chrome.framework   	0x0000000107ec14fe 0x105b5a000 + 37123326
31  com.google.Chrome.framework   	0x0000000107ee48e5 0x105b5a000 + 37267685
32  com.google.Chrome.framework   	0x0000000107adfffd 0x105b5a000 + 33054717
33  com.google.Chrome.framework   	0x000000010678f5b4 0x105b5a000 + 12801460
34  com.google.Chrome.framework   	0x0000000106791d02 0x105b5a000 + 12811522
35  com.google.Chrome.framework   	0x000000010678c07b 0x105b5a000 + 12787835
36  com.google.Chrome.framework   	0x0000000107a92b30 0x105b5a000 + 32738096
37  com.google.Chrome.framework   	0x000000010970798d 0x105b5a000 + 62577037
38  com.google.Chrome.framework   	0x0000000107a91e64 0x105b5a000 + 32734820
39  com.google.Chrome.framework   	0x0000000105b5d7f3 ChromeMain + 179
40  com.google.Chrome.canary      	0x0000000105b2edd1 main + 385
41  libdyld.dylib                 	0x00007fff53c52015 start + 1

Thread 1:
0   libsystem_kernel.dylib        	0x00007fff53da328a __workq_kernreturn + 10
1   libsystem_pthread.dylib       	0x00007fff53f6a009 _pthread_wqthread + 1035
2   libsystem_pthread.dylib       	0x00007fff53f69be9 start_wqthread + 13

Comment 1 by ellyjo...@chromium.org, Aug 7

Labels: -Pri-2 Pri-1
Owner: ellyjo...@chromium.org
Status: Assigned (was: Unconfirmed)
I see this locally; confirming. Investigating now.

Comment 2 by ellyjo...@chromium.org, Aug 7 

Bingo - I was able to talk Canary into uploading a crash report as b70fb8be8315dddd.

Stack:


0x00007fff64a2cb66	(libsystem_kernel.dylib + 0x0001cb66 )	__pthread_kill
0x00007fff649881ad	(libsystem_c.dylib + 0x0005d1ad )	abort
0x00007fff62885f8e	(libc++abi.dylib + 0x00001f8e )	abort_message
0x00007fff62886112	(libc++abi.dylib + 0x00002112 )	default_terminate_handler()
0x00007fff63cc7a4e	(libobjc.A.dylib + 0x00016a4e )	_objc_terminate()
0x00007fff628a17c8	(libc++abi.dylib + 0x0001d7c8 )	std::__terminate(void (*)())
0x00007fff628a126e	(libc++abi.dylib + 0x0001d26e )	__cxa_throw
0x00007fff62867e10	(libc++.1.dylib + 0x0003ae10 )	std::__1::__basic_string_common<true>::__throw_out_of_range() const
0x00007fff62868912	(libc++.1.dylib + 0x0003b912 )	std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> >::basic_string(std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> > const&, unsigned long, unsigned long, std::__1::allocator<char> const&)
0x000000010cbdf2e4	(Google Chrome Framework -string:3238 )	syncer::syncable::Id::GetServerId() const
0x000000010cb97da9	(Google Chrome Framework -uss_migrator.cc:47 )	syncer::MigrateDirectoryDataWithBatchSize(syncer::ModelType, syncer::UserShare*, syncer::ModelTypeWorker*, int)
0x000000010cb7c1b3	(Google Chrome Framework -callback.h:129 )	syncer::ModelTypeRegistry::ConnectNonBlockingType(syncer::ModelType, std::__1::unique_ptr<syncer::DataTypeActivationResponse, std::__1::default_delete<syncer::DataTypeActivationResponse> >)
0x000000010cb7b540	(Google Chrome Framework -bind_internal.h:516 )	base::internal::Invoker<base::internal::BindState<void (syncer::ModelTypeConnector::*)(syncer::ModelType, std::__1::unique_ptr<syncer::DataTypeActivationResponse, std::__1::default_delete<syncer::DataTypeActivationResponse> >), base::WeakPtr<syncer::ModelTypeConnector>, syncer::ModelType, std::__1::unique_ptr<syncer::DataTypeActivationResponse, std::__1::default_delete<syncer::DataTypeActivationResponse> > >, void ()>::RunOnce(base::internal::BindStateBase*)
0x000000010b1d7211	(Google Chrome Framework -callback.h:99 )	base::debug::TaskAnnotator::RunTask(char const*, base::PendingTask*)
0x000000010b1f539e	(Google Chrome Framework -message_loop.cc:431 )	base::MessageLoop::RunTask(base::PendingTask*)
0x000000010b1f5842	(Google Chrome Framework -message_loop.cc:442 )	base::MessageLoop::DoWork()
0x000000010b1f73d8	(Google Chrome Framework -message_pump_default.cc:37 )	base::MessagePumpDefault::Run(base::MessagePump::Delegate*)
0x000000010b21a8e4	(Google Chrome Framework -run_loop.cc:102 )	<name omitted>
0x000000010b25b7a0	(Google Chrome Framework -thread.cc:357 )	base::Thread::ThreadMain()
0x000000010b28d896	(Google Chrome Framework -platform_thread_posix.cc:76 )	base::(anonymous namespace)::ThreadFunc(void*)
0x00007fff64bf4660	(libsystem_pthread.dylib + 0x00003660 )	_pthread_body
0x00007fff64bf450c	(libsystem_pthread.dylib + 0x0000350c )	_pthread_start
0x00007fff64bf3bf8	(libsystem_pthread.dylib + 0x00002bf8 )	thread_start
0x000000010b28d83f	(Google Chrome Framework + 0x023fd83f )

Comment 3 by ellyjo...@chromium.org, Aug 7

Labels: -Pri-1 Pri-0
Owner: mamir@chromium.org
I think it's extremely likely that this was introduced by a410f9f8aa0734e999b9bf8da0ecb3557779a2fe from mamir@. I can't repro this on trunk - I suspect that triggering it requires having an "old" profile of some type.

Elevating to Pri-0, since there doesn't seem to be a way to recover from this state.

Comment 4 by ellyjo...@chromium.org, Aug 7 

 Issue 871700  has been merged into this issue.

Comment 5 by ellyjo...@chromium.org, Aug 7

Cc: gov...@chromium.org
+cc govind@ - this is going to want a canary respin.

Comment 7 by gov...@chromium.org, Aug 7

Cc: abdulsyed@chromium.org
mamir@, Pls merge the fix listed at #6 to canary branch 3515. Also is this crash only applicable to Mac or any other OSs too?

+abdulsyed@ (M70  Desktop Release TPM) to trigger new canary once fix is merged to branch 3515.

Comment 8 by abdulsyed@google.com, Aug 7 

I've merged the change in #6 to 3515. 

https://chromium.googlesource.com/chromium/src.git/+/db389cab3d93ec84817637bfef5ffe3e193bec60

Is this the only fix that's needed? I can trigger new canary once confirmed.

Comment 9 by abdulsyed@google.com, Aug 7 

I've triggered new canary on Mac.
Project Member

Comment 10 by sheriffbot@chromium.org, Aug 22 

Pri-0 bugs are critical regressions or serious emergencies, and this bug has not been updated in three days. Could you please provide an update, or adjust the priority to a more appropriate level if applicable?

If a fix is in active development, please set the status to Started.

Thanks for your time! To disable nags, add the Disable-Nags label.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

Comment 11 by jonathan.wolch@gmail.com, Aug 22 

Huh?

Sent from miPhone

Comment 12 by ellyjo...@chromium.org, Aug 22

Status: Fixed (was: Assigned)
►

Sign in to add a comment