Specific URL leads to deadlock
Reported by
centbrwf...@gmail.com,
Apr 28 2018
|
||||
Issue descriptionUserAgent: Mozilla/5.0 (Windows NT 6.2; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/65.0.3325.181 Safari/537.36 Example URL: http://search.news.cn/#search/0/%E6%B2%A1%E6%9C%89/1/ Steps to reproduce the problem: Visiting the provided URL will lead to infinite URL redirect. It is resulted by https://chromium-review.googlesource.com/c/chromium/src/+/668363/13/url/url_canon_etc.cc. Hope someone can dig into this issue and decide whether this is a Chromium bug. What is the expected behavior? What went wrong? The website won't load. Does it occur on multiple sites: N/A Is it a problem with a plugin? No Did this work before? N/A Does this work in other browsers? Yes Chrome version: 66.0.3359.139 Channel: stable OS Version: 10.0 (Windows 10) Flash Version: Shockwave Flash 29.0 r0
,
May 2 2018
Able to reproduce the issue on reported version 66.0.3359.139, Beta# 67.0.3396.18 and latest chrome# 68.0.3416.0 using Ubuntu 14.04, Windows-10 & Mac 10.12.6, hence providing bisect info Bisect Info: ================ Good build: 63.0.3236.0 Bad build: 63.0.3238.0 You are probably looking for a change made after 507480 (known good), but no later than 507481 (first known bad). https://chromium.googlesource.com/chromium/src/+log/0a918e900a759b04f177cc5b8bca668140751136..f8f6ed59949be4451ee2f5443d8a313f102fde60 Reviewed-on: https://chromium-review.googlesource.com/668363 @Jochen Eisinger: Please confirm the issue and help in re-assigning if it is not related to change provided above. Note: As the owner of the CL(i.e.,: mkwst@chromium.org) is OOO, hence assigning it to reviewer(jochen@chromium.org.) Thanks!
,
May 2 2018
Hrm. Firefox and Chrome both give the same result for `document.location.hash`, which is what that patch changed. I can imagine that the site had some special-casing for Firefox, as the behavior diverged before this patch? I've traced through some of their routing code, and they are setting `window.isFirefox` before calling `navigate(...)`, so I can imagine something's going wrong there. Do we have a contact at this site? My impression is that Chrome's behavior for `window.location.hash` is correct, but talking to the developers would be helpful.
,
May 2 2018
@mkwst, They have technical support +8601063070931 and mail address support@news.cn But I am not sure they can read or speak English. I guess this site worked in IE/Edge and Chrome(till 63), but had issue in Firefox, so they added the special logic for Firefox to prevent deadlock. The deadlock occurs only if you search non-English characters.
,
May 7 2018
I sent them an email. Let's see if they reply. :) |
||||
►
Sign in to add a comment |
||||
Comment 1 by krajshree@chromium.org
, Apr 30 2018