This is a serious security regression. If you are not able to fix this quickly, please revert the change that introduced it.

If this doesn't affect a release branch, or has not been properly classified for severity, please update the Security_Impact or Security_Severity labels, and remove the ReleaseBlock label. To disable this altogether, apply ReleaseBlock-NA.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

ClusterFuzz has detected this issue as fixed in range 508786:508875.

Detailed report: https://clusterfuzz.com/testcase?key=6540472792383488

Fuzzer: mbarbella_js_mutation
Job Type: windows_asan_d8
Platform Id: windows

Crash Type: CHECK failure
Crash Address: 
Crash State:
  start_position == start_position_from_data in preparsed-scope-data.cc
  v8::platform::PrintStackTrace
  v8::internal::ConsumedPreParsedScopeData::GetDataForSkippableFunction
  
Sanitizer: address (ASAN)

Regressed: https://clusterfuzz.com/revisions?job=windows_asan_d8&range=498075:498086
Fixed: https://clusterfuzz.com/revisions?job=windows_asan_d8&range=508786:508875

Reproducer Testcase: https://clusterfuzz.com/download?testcase_id=6540472792383488

See https://github.com/google/clusterfuzz-tools for more information.

If you suspect that the result above is incorrect, try re-doing that job on the test case report page.

ClusterFuzz testcase 6540472792383488 is verified as fixed, so closing issue as verified.

If this is incorrect, please add ClusterFuzz-Wrong label and re-open the issue.

This bug requires manual review: M63 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), gkihumba@(ChromeOS), govind@(Desktop)

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

+awhalley@ (Security TPM) for M63 merge review

There is no CL here. Not sure what needs to be merge here.

awhalley@, could you ptal?

hi - marja@ - some blind grepping suggests https://chromium.googlesource.com/v8/v8/+/dd18faf2cbe430c3731107f3eb130fadbb596064%5E%21/ might be related - mind taking a look?

That commit has already been merged to 63.

https://chromiumdash-staging.googleplex.com/commit/f435a180d199eda0c6777be153aa0ca5541ef599

Double checked the test case, that's exactly what that commit fixes.

Removing "Merge-Review-63" label per comment #13 & #14.

Also applying "merge-merged-6.3" label per comment #13.

This bug has been closed for more than 14 weeks. Removing security view restrictions.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot