Downloading an HTTP archive file from Network tab a second time crashes Chromium
Reported by
lukesw...@gmail.com,
Nov 29 2017
|
|||
Issue descriptionUserAgent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:51.0) Gecko/20100101 Firefox/51.0 Steps to reproduce the problem: 1. Navigate to a website (eg. Google.com) with the developer panel open, and set to the Network tab 2. Right click on a request, and select "Save as HAR with content" 3. Confirm saving the file 4. Repeat step 2 5. Chromium crahses What is the expected behavior? Chromium shouldn't crash and you should be able to save another copy of the HAR content What went wrong? Chromium crashed. I'm not sure why Did this work before? N/A Chrome version: Version 62.0.3202.94 (Developer Build) (64-bit) Channel: stable OS Version: ArchLinux, `uname -a`: Linux 4.13.12-1-ARCH #1 SMP PREEMPT Wed Nov 8 11:54:06 CET 2017 x86_64 GNU/Linux Flash Version:
,
Nov 30 2017
Could you please go to chrome://crashes and copy its content here? We need "Crash Report ID"
,
Nov 30 2017
Are you not able to reproduce this issue? I don't see any crashes reported by Chromium (see screenshot). Perhaps it's not a crash, but something is causing Chromium to shut down incorrectly when I try downloading an HTTP archive file the second time.
,
Dec 1 2017
Your crash reporting is disabled.
,
Dec 1 2017
"Unable to reproduce the issue on the reported chromium version 62.0.3202.94 and on the latest dev 64.0.3280.0 using Windows 10, Mac 10.13.1 and Ubuntu 14.04 with the below mentioned steps. 1. Launched Chromium 2. Navigated to www.google.com 3. Opened dev tools>Network panel 4. Right clicked on a request, and selected ""Save as HAR with content"" 5. Saved the file 6. Repeated step 4 We observed the chromium didn't crash, it saved the file for the second time even.Attaching the screen cast of the same. @Reporter: Could you please have a look at the screen cast and let us know if we have missed any steps in reproducing the issue. Please check the same issue on latest dev in a clear profile and let us know if the issue still persists. Thanks! "
,
Dec 11 2017
|
|||
►
Sign in to add a comment |
|||
Comment 1 by krajshree@chromium.org
, Nov 29 2017