Non responsive server error shows long after successfully navigating to other site in same tab.
Reported by
rene.vae...@gmail.com,
May 23 2016
|
|||||
Issue descriptionUserAgent: Mozilla/5.0 (Windows NT 6.3; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/50.0.2661.102 Safari/537.36 Example URL: http://za.com Steps to reproduce the problem: 1. Open a non responsive site, like one in DoS or simulate it 2. After 10 seconds, navigate to www.google.com or something else 3. Wait a long time (minutes) 4. After some time, the succesfully loaded google site gets replaced with a message that the url entered at step #1 is displayed. What is the expected behavior? 1st Request should be fully aborted What went wrong? It didn't. Did this work before? N/A Chrome version: 50.0.2661.102 Channel: stable OS Version: 6.3 Flash Version: Shockwave Flash 21.0 r0 The za.com domain is currently at the time of submitting this issue, unresponsive from my location, but that does not mean it will at time of reproduction.
,
May 24 2016
I tried. But unfortunately, I can't seem to reproduce it. I even tried to simulate different kinds of faulty webserver network responses. I don't exactly know what happend yesterday when I experienced it, but I know for sure, it happend. First I clicked a link (za.com) that someone posted in an instant message, then when I noticed that indeed the site was down, I clicked a shortcut from Chrome's quick-launch toolbar, navigating to (nu.nl) a news-site. While I was reading the news headlines, the page disappeared and the error message was shown that za.com was unreachable. I guess it could be a number of things, chrome was busy with, when I navigated away from za.com, from nameserver lookup to retreiving content. Sorry, I can't be more helpfull.
,
May 24 2016
Thank you for providing more feedback. Adding requester "zhongyi@chromium.org" for another review and adding "Needs-Review" label for tracking. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
May 24 2016
This sounds like the error page loading is not cleared when the user navigates to a new URL. Unfortunately, I don't so much insight on what's going on with error page loading. mmenke@: could you take a look on this issue and see where potentially this might come from?
,
May 24 2016
This seems more like a navigation issue to me. When the google site commits, the old page should be long gone. Without a repro, not sure if we can make any forward progress here, unfortuantely.
,
May 25 2017
Issue has not been modified or commented on in the last 365 days, please re-open or file a new bug if this is still an issue. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot |
|||||
►
Sign in to add a comment |
|||||
Comment 1 by zhongyi@chromium.org
, May 23 2016