Issue metadata
Sign in to add a comment
|
Save as HAR stuck on Collecting Content
Reported by
ryanholl...@gmail.com,
Mar 29 2018
|
||||||||||||||||||||||||
Issue descriptionUserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_13_3) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/65.0.3325.181 Safari/537.36 Steps to reproduce the problem: 1. Navigate to https://secure1.onlineaccess1.com/aplusfcu/uux.aspx 2. Open Dev Tools, go to Network tab 3. Create traffic by clicking link or refresh page 4. Right click in network traffic and select Save as HAR... 5. Select a location and hit save What is the expected behavior? Expected to have chrome produce a valid HAR file at the location you chose What went wrong? Chrome hangs on "Collecting Content" with a non-responsive red square next to it. A 0 byte file is created with no data. Letting chrome sit for hours produces no additional results. Did this work before? Yes 64 Chrome version: 65.0.3325.181 Channel: stable OS Version: OS X 10.13.3 Flash Version: This is affecting windows users as well.
,
Mar 29 2018
,
Mar 30 2018
Able to reproduce the issue on reported version 65.0.3325.181 and beta 66.0.3359.66 and the same is not seen on latest canary 67.0.3383.0 using Windows 10, Ubuntu 14.04 & Mac 10.13.3, hence providing reverse bisect info Reverse Bisect Info: ================ Last Bad build: 67.0.3362.0 First Good build: 67.0.3364.0 You are probably looking for a change made after 541195 (known good), but no later than 541196 (first known bad). https://chromium.googlesource.com/chromium/src/+log/1fb0de50112615910add049a6b8223c2f13f03ef..9d2e70dbef548b2d6bff1952c75b56e6419300fd Reviewed on: https://chromium-review.googlesource.com/947255 @Eugene Ostroukhov: Please confirm the issue and help in re-assigning if it is not related to your change, please help in merging it to M-65 & M-66 if applicable Adding ReleaseBlock-Stable as it seems recent break, feel free to remove it if not applicable. Thanks!
,
Mar 30 2018
,
Mar 30 2018
I confirmed this bug exists in 65 and 66, requesting merge.
,
Mar 30 2018
This bug requires manual review: M66 has already been promoted to the beta branch, so this requires manual review Please contact the milestone owner if you have questions. Owners: cmasso@(Android), cmasso@(iOS), josafat@(ChromeOS), abdulsyed@(Desktop) For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Apr 2 2018
Approving merge for M66. Branch:3359
,
Apr 2 2018
Punting the bug to M66, since at this point we aren't planning any M65 respins at the moment.
,
Apr 2 2018
,
Apr 2 2018
Rejecting merge to M65 based on comment #8.
,
Apr 6 2018
This issue has been approved for a merge. Please merge the fix to any appropriate branches as soon as possible! If all merges have been completed, please remove any remaining Merge-Approved labels from this issue. Thanks for your time! To disable nags, add the Disable-Nags label. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Apr 9 2018
This issue has been approved for a merge. Please merge the fix to any appropriate branches as soon as possible! If all merges have been completed, please remove any remaining Merge-Approved labels from this issue. Thanks for your time! To disable nags, add the Disable-Nags label. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Apr 11 2018
|
|||||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||||
Comment 1 by viswa.karala@chromium.org
, Mar 29 2018