Chrome shuts down while sending test expect-ct request second time.
Reported by
ah...@netsparker.com,
Mar 19 2018
|
||||||
Issue description
Chrome Version : 65.0.3325.146
OS Version: 10.0
URLs (if applicable) : chrome://net-internals/#hsts
Other browsers tested:
Add OK or FAIL after other browsers where you have tested this issue:
Safari:
Firefox:
IE/Edge:
What steps will reproduce the problem?
1. Send test Expect-CT report
2. Send test Expect-CT report second time
3. And chrome shuts down.
What is the expected result?
What happens instead of that?
Please provide any additional information below. Attach a screenshot if
possible.
UserAgentString: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/65.0.3325.146 Safari/537.36
,
Mar 20 2018
Thanks for filing the issue!
Able to reproduce the issue on reported chrome version 65.0.3325.146 and on the latest canary 67.0.3375.0 using Windows 10, Ubuntu 14.04 and Mac 10.13.1.
The option "Send test Expect-CT report" under Domain Security Policy after navigating to chrome://net-internals/#hsts is available from version 65.0.3311.0, where the crash is seen after sending the request for second time. As the issue is seen from the introduction of this feature considering it as Non-Regression and marking it as Untriaged.
Tentatively adding component "Blink>Layout".
Note: As this is related to crash
1.Changing the priority of the bug to 1
2.Adding M-65,FoundIn-65,FoundIn-66,FoundIn-67,Target-65,Target-66 and Target-67
labels.
Please feel free to change/Remove(labels) if not applicable.
,
Mar 21 2018
,
Mar 22 2018
estark@: Emily, this feature is introduced by f2f09f6acfc74dfce06fece0245520b2c63e809a. Could you take a look?
,
Mar 22 2018
,
Mar 22 2018
|
||||||
►
Sign in to add a comment |
||||||
Comment 1 by krajshree@chromium.org
, Mar 20 2018