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

Issue 612064 link

Starred by 1 user
Status: WontFix
Owner: ----
Closed: May 2016
Cc:
█ ashej...@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Mac
Pri: 2
Type: Bug



Sign in to add a comment

Chrome Crashes on Launching

Reported by tim.graf...@gmail.com, May 16 2016 
UserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_11_4) AppleWebKit/601.5.17 (KHTML, like Gecko) Version/9.1 Safari/601.5.17

Steps to reproduce the problem:
1. Launch Chrome
2. It crashes

What is the expected behavior?
The browser opens and works

What went wrong?
Process:               Google Chrome [2335]
Path:                  /Applications/Google Chrome.app/Contents/MacOS/Google Chrome
Identifier:            com.google.Chrome
Version:               50.0.2661.102 (2661.102)
Code Type:             X86-64 (Native)
Parent Process:        ??? [1]
Responsible:           Google Chrome [2335]
User ID:               501

Date/Time:             2016-05-15 18:40:04.705 -0700
OS Version:            Mac OS X 10.11.4 (15E65)
Report Version:        11
Anonymous UUID:        0C1BE5DA-1093-70D2-2C62-21BB4D0C0DF7

Sleep/Wake UUID:       A0E914EA-02AB-4C4C-AC7B-43FE41B5DFA1

Time Awake Since Boot: 21000 seconds
Time Since Wake:       6200 seconds

System Integrity Protection: enabled

Crashed Thread:        12  WorkerPool/29187

Exception Type:        EXC_BAD_ACCESS (SIGSEGV)
Exception Codes:       EXC_I386_GPFLT

Thread 0:: CrBrowserMain  Dispatch queue: com.apple.main-thread
0   com.google.Chrome.framework   	0x000000010f6a7680 0x10c4f7000 + 52102784
1   com.google.Chrome.framework   	0x000000010c642755 0x10c4f7000 + 1357653
2   com.google.Chrome.framework   	0x000000010c58bf02 0x10c4f7000 + 610050
3   com.google.Chrome.framework   	0x000000010c58bc0c 0x10c4f7000 + 609292
4   com.google.Chrome.framework   	0x000000010fbe46ed 0x10c4f7000 + 57595629
5   com.google.Chrome.framework   	0x000000010fe8b3c7 0x10c4f7000 + 60376007
6   com.google.Chrome.framework   	0x000000010fbe4c04 0x10c4f7000 + 57596932
7   com.google.Chrome.framework   	0x000000010fbe8a5a 0x10c4f7000 + 57612890
8   com.google.Chrome.framework   	0x000000010fbe24c5 0x10c4f7000 + 57586885
9   com.google.Chrome.framework   	0x000000010ca0af7c 0x10c4f7000 + 5324668
10  com.google.Chrome.framework   	0x000000010ca0a506 0x10c4f7000 + 5321990
11  com.google.Chrome.framework   	0x000000010c4f9b92 ChromeMain + 66
12  com.google.Chrome             	0x000000010c290d42 main + 530
13  com.google.Chrome             	0x000000010c290b24 0x10c290000 + 2852

Thread 1:
0   libsystem_kernel.dylib        	0x00007fff976c75e2 __workq_kernreturn + 10
1   libsystem_pthread.dylib       	0x00007fff8855a578 _pthread_wqthread + 1283
2   libsystem_pthread.dylib       	0x00007fff88558341 start_wqthread + 13

Thread 2:: Dispatch queue: com.apple.libdispatch-manager
0   libsystem_kernel.dylib        	0x00007fff976c0f72 mach_msg_trap + 10
1   libsystem_kernel.dylib        	0x00007fff976c03b3 mach_msg + 55
2   libsystem_kernel.dylib        	0x00007fff976b603c _kernelrpc_mach_port_request_notification + 120
3   libdispatch.dylib             	0x00007fff96923fcd _dispatch_kevent_mach_notify_resume + 314
4   libdispatch.dylib             	0x00007fff969241bd _dispatch_kevent_unregister + 191
5   libdispatch.dylib             	0x00007fff969270b4 _dispatch_mach_disconnect + 41
6   libdispatch.dylib             	0x00007fff96926f8f _dispatch_mach_cancel + 58
7   libdispatch.dylib             	0x00007fff96922416 _dispatch_mach_invoke + 918
8   libdispatch.dylib             	0x00007fff96920200 _dispatch_queue_drain + 1207
9   libdispatch.dylib             	0x00007fff969211df _dispatch_mgr_queue_drain + 32
10  libdispatch.dylib             	0x00007fff969210ba _dispatch_mgr_invoke + 45
11  libdispatch.dylib             	0x00007fff96920dcd _dispatch_mgr_thread + 52

Thread 3:
0   libsystem_kernel.dylib        	0x00007fff976c75e2 __workq_kernreturn + 10
1   libsystem_pthread.dylib       	0x00007fff8855a578 _pthread_wqthread + 1283
2   libsystem_pthread.dylib       	0x00007fff88558341 start_wqthread + 13

Thread 4:
0   libsystem_kernel.dylib        	0x00007fff976c0f72 mach_msg_trap + 10
1   libsystem_kernel.dylib        	0x00007fff976c03b3 mach_msg + 55
2   com.google.Chrome.framework   	0x0000000111188370 0x10c4f7000 + 80286576
3   com.google.Chrome.framework   	0x000000011118861b 0x10c4f7000 + 80287259
4   com.google.Chrome.framework   	0x00000001111845f8 0x10c4f7000 + 80270840
5   libsystem_pthread.dylib       	0x00007fff8855a99d _pthread_body + 131
6   libsystem_pthread.dylib       	0x00007fff8855a91a _pthread_start + 168
7   libsystem_pthread.dylib       	0x00007fff88558351 thread_start + 13

Thread 5:
0   libsystem_kernel.dylib        	0x00007fff976c75e2 __workq_kernreturn + 10
1   libsystem_pthread.dylib       	0x00007fff8855a578 _pthread_wqthread + 1283
2   libsystem_pthread.dylib       	0x00007fff88558341 start_wqthread + 13

Thread 6:
0   libsystem_kernel.dylib        	0x00007fff976c75e2 __workq_kernreturn + 10
1   libsystem_pthread.dylib       	0x00007fff8855a578 _pthread_wqthread + 1283
2   libsystem_pthread.dylib       	0x00007fff88558341 start_wqthread + 13

Thread 7:

Thread 8:
0   libsystem_kernel.dylib        	0x00007fff976c6db6 __psynch_cvwait + 10
1   libsystem_pthread.dylib       	0x00007fff8855b75e _pthread_cond_wait + 821
2   com.apple.Foundation          	0x00007fff9ad35ac5 -[NSLock lockBeforeDate:] + 427
3   com.google.Keystone.Registration	0x0000000118835c37 -[KSRegistrationAction keystoneInstallationLockThread] + 272
4   com.apple.Foundation          	0x00007fff9ac9fd64 __NSThread__start__ + 1351
5   libsystem_pthread.dylib       	0x00007fff8855a99d _pthread_body + 131
6   libsystem_pthread.dylib       	0x00007fff8855a91a _pthread_start + 168
7   libsystem_pthread.dylib       	0x00007fff88558351 thread_start + 13

Thread 9:: NetworkConfigWatcher
0   libsystem_kernel.dylib        	0x00007fff976c0f72 mach_msg_trap + 10
1   libsystem_kernel.dylib        	0x00007fff976c03b3 mach_msg + 55
2   com.apple.CoreFoundation      	0x00007fff9486f1c4 __CFRunLoopServiceMachPort + 212
3   com.apple.CoreFoundation      	0x00007fff9486e68c __CFRunLoopRun + 1356
4   com.apple.CoreFoundation      	0x00007fff9486ded8 CFRunLoopRunSpecific + 296
5   com.apple.Foundation          	0x00007fff9ac8edd9 -[NSRunLoop(NSRunLoop) runMode:beforeDate:] + 270
6   com.google.Chrome.framework   	0x000000010ca494de 0x10c4f7000 + 5579998
7   com.google.Chrome.framework   	0x000000010ca48cc4 0x10c4f7000 + 5577924
8   com.google.Chrome.framework   	0x000000010ca8a0c3 0x10c4f7000 + 5845187
9   com.google.Chrome.framework   	0x000000010ca747ed 0x10c4f7000 + 5756909
10  com.google.Chrome.framework   	0x000000010caac0d8 0x10c4f7000 + 5984472
11  com.google.Chrome.framework   	0x000000010caa84d7 0x10c4f7000 + 5969111
12  libsystem_pthread.dylib       	0x00007fff8855a99d _pthread_body + 131
13  libsystem_pthread.dylib       	0x00007fff8855a91a _pthread_start + 168
14  libsystem_pthread.dylib       	0x00007fff88558351 thread_start + 13

Thread 10:: DnsConfigService
0   libsystem_kernel.dylib        	0x00007fff976c7eca kevent + 10
1   com.google.Chrome.framework   	0x000000010cada387 0x10c4f7000 + 6173575
2   com.google.Chrome.framework   	0x000000010cad7c4b 0x10c4f7000 + 6163531
3   com.google.Chrome.framework   	0x000000010ca48191 0x10c4f7000 + 5575057
4   com.google.Chrome.framework   	0x000000010ca8a0c3 0x10c4f7000 + 5845187
5   com.google.Chrome.framework   	0x000000010ca747ed 0x10c4f7000 + 5756909
6   com.google.Chrome.framework   	0x000000010caac0d8 0x10c4f7000 + 5984472
7   com.google.Chrome.framework   	0x000000010caa84d7 0x10c4f7000 + 5969111
8   libsystem_pthread.dylib       	0x00007fff8855a99d _pthread_body + 131
9   libsystem_pthread.dylib       	0x00007fff8855a91a _pthread_start + 168
10  libsystem_pthread.dylib       	0x00007fff88558351 thread_start + 13

Thread 11:: CrShutdownDetector
0   libsystem_kernel.dylib        	0x00007fff976c8362 read + 10
1   com.google.Chrome.framework   	0x000000010c8580ff 0x10c4f7000 + 3543295
2   com.google.Chrome.framework   	0x000000010caa84d7 0x10c4f7000 + 5969111
3   libsystem_pthread.dylib       	0x00007fff8855a99d _pthread_body + 131
4   libsystem_pthread.dylib       	0x00007fff8855a91a _pthread_start + 168
5   libsystem_pthread.dylib       	0x00007fff88558351 thread_start + 13

Thread 12 Crashed:: WorkerPool/29187
0   libresolv.9.dylib             	0x00007fff93361215 res_9_getservers + 68
1   com.google.Chrome.framework   	0x000000010ce6d146 0x10c4f7000 + 9920838
2   com.google.Chrome.framework   	0x000000010ce6d57e 0x10c4f7000 + 9921918
3   ???                           	0x73682e74656e2e74 0 + 8315947789392424564

Thread 13:: WorkerPool/29443
0   libsystem_kernel.dylib        	0x00007fff976c6db6 __psynch_cvwait + 10
1   libsystem_pthread.dylib       	0x00007fff8855b75e _pthread_cond_wait + 821
2   com.google.Chrome.framework   	0x000000010ca9a4cb 0x10c4f7000 + 5911755
3   com.google.Chrome.framework   	0x000000010caadfbe 0x10c4f7000 + 5992382
4   com.google.Chrome.framework   	0x000000010caae4b2 0x10c4f7000 + 5993650
5   com.google.Chrome.framework   	0x000000010caa84d7 0x10c4f7000 + 5969111
6   libsystem_pthread.dylib       	0x00007fff8855a99d _pthread_body + 131
7   libsystem_pthread.dylib       	0x00007fff8855a91a _pthread_start + 168
8   libsystem_pthread.dylib       	0x00007fff88558351 thread_start + 13

Thread 12 crashed with X86 Thread State (64-bit):
  rax: 0x2e316473682e7465  rbx: 0x0000000000000001  rcx: 0x0000000000000000  rdx: 0x2e316473682e7466
  rdi: 0x0000700001bb5a88  rsi: 0x0000700001bb5790  rbp: 0x0000700001bb5730  rsp: 0x0000700001bb5728
   r8: 0x0000000000000003   r9: 0x0000700001bb5a9d  r10: 0x0000000000000000  r11: 0x00007fff933611d1
  r12: 0x00007fcaf36227d0  r13: 0x00007fcaf36227a0  r14: 0x0000700001bb5a88  r15: 0x0000000000000002
  rip: 0x00007fff93361215  rfl: 0x0000000000010246  cr2: 0x00007fff78a3f6c0

Logical CPU:     6
Error Code:      0x00000000
Trap Number:     13

...

Model: MacBookPro11,3, BootROM MBP112.0138.B17, 4 processors, Intel Core i7, 2.6 GHz, 16 GB, SMC 2.19f12
Graphics: Intel Iris Pro, Intel Iris Pro, Built-In
Graphics: NVIDIA GeForce GT 750M, NVIDIA GeForce GT 750M, PCIe, 2048 MB
Memory Module: BANK 0/DIMM0, 8 GB, DDR3, 1600 MHz, 0x80AD, 0x484D54343147533641465238412D50422020
Memory Module: BANK 1/DIMM0, 8 GB, DDR3, 1600 MHz, 0x80AD, 0x484D54343147533641465238412D50422020
AirPort: spairport_wireless_card_type_airport_extreme (0x14E4, 0x134), Broadcom BCM43xx 1.0 (7.21.95.175.1a6)
Bluetooth: Version 4.4.4f4 17685, 3 services, 27 devices, 1 incoming serial ports
Network Service: Wi-Fi, AirPort, en0
Serial ATA Device: APPLE SSD SM0512F, 500.28 GB
USB Device: USB 3.0 Bus
USB Device: Apple Internal Keyboard / Trackpad
USB Device: BRCM20702 Hub
USB Device: Bluetooth USB Host Controller
Thunderbolt Bus: MacBook Pro, Apple Inc., 17.1

Crashed report ID: No

How much crashed? Whole browser

Is it a problem with a plugin? No 

Did this work before? Yes 

Chrome version: <Copy from: 'about:version'>  Channel: stable
OS Version: OS X 10.11.4
Flash Version: Shockwave Flash 21.0 r0

Comment 1 by ashej...@chromium.org, May 16 2016

Cc: ashej...@chromium.org
Labels: Needs-Feedback
Thanks for the report. I am unable to reproduce the above issue on Mac 10.11.4 with chrome version 50.0.2661.102. I would request you to please try the above scenario by creating a new user from chrome://settings and let us know if the issue still persists.

Also, if it does then I would request you to provide crash id from chrome://crashes ?

I really appreciate your help.

Thank you!

Comment 2 by rsesek@chromium.org, May 16 2016 

Please attach the crash report as a file rather than pasting it inline. Since the bottom of the report has been trimmed, we can't actually take action on this.

Comment 3 by tim.graf...@gmail.com, May 16 2016 

Thanks for the reply.  I've attached the crash report as a file.  Also I can't find a crash ID.  I've followed the direction from this link.

https://www.chromium.org/for-testers/bug-reporting-guidelines/reporting-crash-bug

Since the browser never actually opens I can't get the crash ID from Chrome.  I attached a screenshot of the window I get that tells me Google Chrome quit unexpectedly.  Also there doesn't seem to be a profile folder under ~/Library/Application Support/Google/Chrome since I tried uninstalling and reinstalling Chrome several times.

However user the following folder,

~/Library/Application Support/Google/Chrome/Crashpad/completed

There are .dmp files if those are helpful.  I have attached one.

I also tried creating a new user on my mack and launching Chrome but the same thing happens.  My wife who has the same Mac and same OS version, etc. is also experiencing the same issue.

I hope this helps.

Thanks,
Tim
ChromeCrash.txt
58.1 KB View Download
Screen Shot 2016-05-16 at 9.00.52 AM.png
534 KB View Download
a62cf589-38ae-4e5f-a41d-c26d4e70e972.dmp
212 KB Download

Comment 4 by rsesek@chromium.org, May 16 2016

Components: Internals>Network>DNS
Thanks. You can get the crash IDs from about:crashes, but that only works if the browser launches. Thanks for attaching the .dmp, since that's as good as a crash ID.

Thread 11 Crashed:: WorkerPool/29443
0   libresolv.9.dylib             	0x00007fff96e46215 res_9_getservers + 68
1   com.google.Chrome.framework   	0x0000000101060146 net::internal::ConvertResStateToDnsConfig(__res_9_state const&, net::DnsConfig*) + dns_config_service_posix.cc:458
2   com.google.Chrome.framework   	0x000000010106057e net::internal::DnsConfigServicePosix::ConfigReader::DoWork() + dns_config_service_posix.cc:127
3   ???                           	0x73682e74656e2e74 0 + 8315947789392424564
Project Member

Comment 5 by sheriffbot@chromium.org, May 18 2016

Labels: -Needs-Feedback Needs-Review
Owner: ashej...@chromium.org
Thank you for providing more feedback. Adding requester "ashejole@chromium.org" for another review and adding "Needs-Review" label for tracking.

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

Comment 6 by tim.graf...@gmail.com, May 19 2016 

Seeing that the issue was DNS related, I read about Comcast/Xfinity having issues for other people.  So I set the DNS setting on my WiFi router to the Google public DNS and Chrome is working now.  

https://developers.google.com/speed/public-dns/docs/using

Of course, it would have been better if Chrome did not crash but I'm glad to have my favorite browser back.  I thought I would at least provide this information in the event it may help find the root cause or help someone else.

Comment 7 by ashej...@chromium.org, May 20 2016

Labels: -Needs-Review
Owner: ----
Status: WontFix (was: Unconfirmed)
Thanks for the update, based on the same in comment #6, closing the above issue.

Thank you!
►

Sign in to add a comment