Comment #3 on issue 15602 by [email protected]: Crash -  
net::ProxyConfigServiceWin::GetProxyConfig(net::ProxyConfig *)
http://code.google.com/p/chromium/issues/detail?id=15602

This looks like memory corruption in the browser process.

Note that the crash actually happens in ntdll!RtlAllocateHeap+0x9bb, as a  
result of calling
winhttp!WinHttpGetIEProxyConfigForCurrentUser.

0:006> kb
   *** Stack trace for last set context - .thread/.cxr resets it
ChildEBP RetAddr  Args to Child
012feec4 7c809a7f 00150000 00140008 000009e4 ntdll!RtlAllocateHeap+0x9bb
012fef10 76e95e52 00000040 000009e4 76e9716b kernel32!LocalAlloc+0x58
012fef1c 76e9716b 00185978 00000330 00000000 rasman!GetRequestBuffer+0xd
012fef54 76e94a63 00000000 00000037 012fefac rasman!SubmitRequest+0x21
012fef70 76ee41bb 00000000 00000000 012fefac rasman!RasConnectionEnum+0x2b
012feffc 4d503d0a 00185978 012ff014 041d0004  
rasapi32!RasEnumConnectionsW+0xee
012ff018 4d5022df 00c9b540 7c839ad8 7c809f80  
winhttp!RasEnumConnHelp::Enum+0x48
012ff038 4d4f87f9 012ff0ac 00c9b540 0000003c  
winhttp!GetActiveConnectionName+0x70
012ff084 02202089 012ff09c 012ff270 00c9b540  
winhttp!WinHttpGetIEProxyConfigForCurrentUser+0x5b
012ff13c 021f61e0 012ff270 96de4618 00c9b540  
chrome_1c30000!net::ProxyConfigServiceWin::GetProxyConfig+0x27
[c:\b\slave\chrome-official-2\build\src\net\proxy\proxy_config_service_win.cc  
@  
31]

This can't be a bug in the caller of  
WinHttpGetIEProxyConfigForCurrentUser(), since I verified that the sole  
argument to
WinHttpGetIEProxyConfigForCurrentUser() is correct (it's just a pointer to  
a zero-ed output structure on the stack).


--
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
-~----------~----~----~----~------~----~------~--~---

Reply via email to