Comment #50 on issue 12189 by [email protected]: Retrieving the proxy settings on windows can block IO thread for seconds. http://code.google.com/p/chromium/issues/detail?id=12189
@wtc: Hm, interesting wording. On all the systems I have tested, that was not the case. (That would be a pretty strange API to have, since that field is already used to output the user specified PAC location, which can be set in conjunction to auto-detect. Also you can't know which URL to settle on until you have tried them) @darthandroid: Definitely sounds like that function is having a network dependency for you. Could you run Wireshark (the packet tracer) to see what it is being sent out onto the wire? I could imagine it either trying to send a DHCP NOTIFY (option 252), or maybe just asking DNS to resolve "wpad". (1) Close down your network applications (browser etc), then start capturing in Wireshark (ctrl-E). (2) run dump_proxy.exe (3) Stop capturing in Wireshark (ctrl-E). If you can attach that output, and the output from dump_proxy, that would be great, and we can take a look through the packets. Also if you sort by protocol (click the protocol column), you can eyeball and check for any entries under DHCP or DNS protocol. (Those are the likeliest things I could imagine it trying to do). @gwilson: Yeah, we may have to move this off IO thread. But I am still pretty unhappy with that solution, since we would STILL have an unacceptably large latency, it just wouldn't p0wn the browser. Really we need for our retrieval of proxy settings to be instantaneous and without network dependency, since until we know the proxy settings we can't even fulfill any requests. -- 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
