Comment #39 on issue 12189 by [email protected]: Renderer freezes
http://code.google.com/p/chromium/issues/detail?id=12189
@darthandroid: Thankyou!
That confirms the theory that WinHttpGetIEProxyConfigForCurrentUser() is
causing the problem.
So the next question, is why it runs slowly on some system.
One possibility is there could be some third party module (download
accelerator/firewall/proxy settings switcher/antivirus/etc..) that changes
the
behavior of that function.
If you experience this, could you send me a list of the modules loaded into
chrome browser process?
You can get that information as follows:
(1) Lookup the browser PID by navigating to about:memory (it will be in
the first row).
(2) At a command prompt execute:
ntsd -pvr -p PID -logo modulelist.txt -c "lm v; q"
(where PID is the number found by step 1.)
This will save a file called "modulelist.txt", with all the module
information, please attach that.
Thanks.
--
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
