Comment #16 on issue 22083 by [email protected]: Chrome: Crash Report -
Stack Signature: -24A0B , net::SystemHostResolverProc
http://code.google.com/p/chromium/issues/detail?id=22083
I crunched the numbers for crash reports from 245, 249.0, 249.4 (about 500
in total)
The distribution of hosts passed to getaddrinfo() in the crash reports is
entirely boring:
* 70% of the crash reports have a unique host name.
* The top five hostnames are:
5.0% "www.dailymotion.com"
2.2% "www.blogger.com"
1.8% "www.google.com"
1.3% "www.megaupload.com"
1.1% "www.redtube.com"
* The top TLDs are:
66.0% "*.com"
8.1% "*.net"
7.2% "*.ru"
* All hosts are regular ASCII strings, with lengths <= 37 characters.
(so nothing crazy being passed to getaddrinfo()).
I looked for third party DLLs on the crashed thread's callstack, and there
isn't strong
evidence to suggest third party code as the major contribor to this crash.
At best, around
50% of the crashes could be blamed to third party DLLs hooking into winsock:
* 35.2% nvlsp.dll
* 10.7% tcpipdog[0-2].dll
* 9.0% imon.dll
* 3.1% securenet.dll
* 2.2% idmmbc.dll
* 1.7% rdolib.dll
* 1.8% betsp.dll
* 1.5% grabkernel.dll
* 0.9% guard32.dll
* 0.7% vlsp.dll
This is smelling more and more like a Windows system library bug...
--
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this issue.
You may adjust your issue notification preferences at:
http://code.google.com/hosting/settings
--
Automated mail from issue updates at http://crbug.com/
Subscription options: http://groups.google.com/group/chromium-bugs
