New issue
Advanced search Search tips

Issue 638734 link

Starred by 1 user
Status: WontFix
Owner: ----
Closed: Oct 2016
Components:
EstimatedDays: ----
NextAction: ----
OS: Mac
Pri: 2
Type: Bug



Sign in to add a comment

Crash in res_9_getservers

Reported by valod...@gmail.com, Aug 17 2016 
UserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:47.0) Gecko/20100101 Firefox/47.0

Steps to reproduce the problem:
1. Run Google Chrome in my home network
Thats all.

In work network Chrome works.
If I switch off WiFi Chrome starts, but crash immediatelly when I enable WiFi.

What is the expected behavior?

What went wrong?
Browser crases with:

Exception Type:        EXC_BAD_ACCESS (SIGSEGV)
Exception Codes:       EXC_I386_GPFLT

Thread 7 Crashed:: WorkerPool/29443
0   libresolv.9.dylib             	0x00007fff917c0215 res_9_getservers + 68
1   com.google.Chrome.framework   	0x0000000102ac4554 0x102166000 + 9823572
2   com.google.Chrome.framework   	0x0000000102ac490e 0x102166000 + 9824526
3   com.google.Chrome.framework   	0x0000000102ad6ae6 0x102166000 + 9898726
4   com.google.Chrome.framework   	0x000000010274bf05 0x102166000 + 6184709
5   com.google.Chrome.framework   	0x0000000102745ed7 0x102166000 + 6160087
6   libsystem_pthread.dylib       	0x00007fff8f61999d _pthread_body + 131
7   libsystem_pthread.dylib       	0x00007fff8f61991a _pthread_start + 168
8   libsystem_pthread.dylib       	0x00007fff8f617351 thread_start + 13

Crashed report ID: a2ea712100000000 (1a606511-203b-45d4-a6c6-961275cad54b)

How much crashed? Whole browser

Is it a problem with a plugin? No 

Did this work before? N/A 

Chrome version: 52.0.2743.116 (2743.116)  Channel: stable
OS Version: OS X 10.11.6
Flash Version: 

Viber has same issue in same function (res_9_getservers), but other network connected applications (Firefox, Skype, Telegram) work.

Comment 1 by rsesek@chromium.org, Aug 18 2016

Components: Internals>Network>DNS
Thread 6 CRASHED [EXC_BAD_ACCESS / 0x0000000d @ 0x00007fff917c0215 ] MAGIC SIGNATURE THREAD
0x00007fff917c0215	(libresolv.9.dylib + 0x00013215 )	res_9_getservers
0x0000000102293553	(Google Chrome Framework -dns_config_service_posix.cc:467 )	net::internal::ConvertResStateToDnsConfig(__res_9_state const&, net::DnsConfig*)
0x000000010229390d	(Google Chrome Framework -dns_config_service_posix.cc:134 )	net::internal::DnsConfigServicePosix::ConfigReader::DoWork()
0x00000001022a5ae5	(Google Chrome Framework -serial_worker.cc:61 )	net::SerialWorker::DoWorkJob()
0x0000000101f1af04	(Google Chrome Framework -callback.h:397 )	base::(anonymous namespace)::WorkerThread::ThreadMain()
0x0000000101f14ed6	(Google Chrome Framework -platform_thread_posix.cc:70 )	base::(anonymous namespace)::ThreadFunc(void*)
0x00007fff8f61999c	(libsystem_pthread.dylib + 0x0000399c )	_pthread_body
0x00007fff8f619919	(libsystem_pthread.dylib + 0x00003919 )	_pthread_start
0x00007fff8f617350	(libsystem_pthread.dylib + 0x00001350 )	thread_start
0x0000000101f14e7f	(Google Chrome Framework + 0x005dfe7f )

Comment 2 by valod...@gmail.com, Aug 18 2016 

Looks like it's Max OS (libresolv) bug. If search domains configuration is (order is important):

 search domain[0] : www.huaweimobilewifi.comwww.huaweimobilewifi.comwww.huaweimobilewifi.comwww.huaweimobilewifi.com
  search domain[1] : huaweimobilewifi.comwww.huaweimobilewifi.comwww.huaweimobilewifi.comwww.huaweimobilewifi.com
  search domain[2] : comwww.huaweimobilewifi.comwww.huaweimobilewifi.comwww.huaweimobilewifi.com
  search domain[3] : huaweimobilewifi.comwww.huaweimobilewifi.comwww.huaweimobilewifi.com
  search domain[4] : comwww.huaweimobilewifi.comwww.huaweimobilewifi.com
  search domain[5] : huaweimobilewifi.comwww.huaweimobilewifi.com
  search domain[6] : comwww.huaweimobilewifi.com

res_ninit fails to init __res_state properly and __res_state._u._ext.ext->nsaddrs became corrupted.
Workaround is to change search domain manually to any reasonable value.

Comment 3 by juliatut...@chromium.org, Oct 5 2016

Status: WontFix (was: Unconfirmed)
Sounds plausible enough :) Reopen if it seems to happen with a more reasonable search domain configuration.
►

Sign in to add a comment