Status: Unconfirmed Owner: ---- Labels: Type-Bug Pri-2 Area-Undefined
New issue 31769 by Christopher.Eatinger: Killing a SOCKS proxy used by chromium causes it to crash
http://code.google.com/p/chromium/issues/detail?id=31769 SRWare Iron 4.0.275.2 (Developer Build 35171) WebKit 532.8 V8 2.0.4 User Agent Mozilla/5.0 (X11; U; Linux i686; en-US) AppleWebKit/532.8 (KHTML, like Gecko) Iron/4.0.275.2 Chrome/4.0.275.2 Safari/532.8 Other browsers tested: Add OK or FAIL after other browsers where you have tested this issue: Firefox 3.x: OK What steps will reproduce the problem? 1. ssh -D 8008 remote.host 2. iron --proxy-server=socks5://127.0.0.1:8008 3. kill `pgrep -f "ssh -D 8008"` What is the expected result? When the proxy that a web-browser is using stops responding the browser should respond just as if the user's network connection had been disconnected. Namely, it should keep sending page requests, and returning errors when it receives no responses. What happens instead? A 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
