Updates:
Status: Fixed
Comment #9 on issue 5688 by [email protected]: Too many resource requests
by renderer can cause memory exhaustion and eventual browser crash.
http://code.google.com/p/chromium/issues/detail?id=5688
The browser becoming unresponsive and crashing is fixed by r9298.
The related sub-issues have been filed as:
---- Throttle requests renderer-side -----
(Without which you can still memory exhaust + crash the renderer process)
https://bugs.webkit.org/show_bug.cgi?id=23372
---- Actually cancel PAC requests ----
(Without which proxy resolving slowness lingers even after closing the
offending tab)
http://code.google.com/p/chromium/issues/detail?id=7461
--
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
-~----------~----~----~----~------~----~------~--~---
