Comment #4 on issue 22083 by [email protected]: Chrome: Crash Report -
Stack Signature: -24A0B , net::SystemHostResolverProc
http://code.google.com/p/chromium/issues/detail?id=22083
Yeah we have had these for a while...
I looked into these some time ago, and the crash was happening somewhere
deep inside of getaddrinfo(), in the heap
management code.
I believe this is a case where a system library outside of our control is
bugging-out (perhaps incited by some third-party
crapware?).
The arguments we pass into getaddrinfo() are really straightforward:
* two pointers to stack-allocated objects
* one pointer to a null-terminated string backed by a std::string.
Perhaps the bug is tickled by trying to resolve particular hosts (long
length? non-ascii characters?).
We could put this theory to the test by pushing the host string onto the
stack before calling getaddrinfo(), and see if there is any
pattern in which host strings are causing the crash!
--
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
-~----------~----~----~----~------~----~------~--~---
