Automatically applying components based on crash stacktrace and information from OWNERS files.

If this is incorrect, please apply the Test-Predator-Wrong-Components label.

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

@herb: Could you help find an owner for this? Thanks.

(Looks like I missed adding the CC, sorry. Retrying.)

@herb: Could you help find an owner for this? Thanks.

Access denied when try to look at the detailed report:

You (email=herb@google.com) are not authorized to access this page!

Please contact clusterfuzz-dev [at] chromium [dot] org. If you are trying to access the testcase for a bug, make sure that you are marked as Owner.

Switching you to owner for now. That should let you access the report, but let me know if it doesn't work.

Still access denied. :-(

In addition, tried logging out and logging back in. Try on both linux and mac.

This looks like it may be a dupe of  crbug.com/791317 . Waiting for clusterfuzz to see if it's already verified as fixed or not.

Clusterfuzz says this is fixed already, but since it doesn't appear to have de-duped them I'd like to wait for confirmation before closing.

Hey, I cannot see the details here.

You (email=mtklein@chromium.org) are not authorized to access this page!

Please contact clusterfuzz-dev [at] chromium [dot] org. If you are trying to access the testcase for a bug, make sure that you are marked as Owner.

Switch account
Logout

Can't do much without that detailed report.  Happy to investigate if we get that working.

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

Fuzzer: attekett_surku_fuzzer
Job Type: linux_msan_chrome
Platform Id: linux

Crash Type: Use-of-uninitialized-value
Crash Address: 
Crash State:
  sk_unpremul
  sk_start_pipeline
  SkScan::FillIRect
  
Sanitizer: memory (MSAN)

Recommended Security Severity: Medium

Regressed: https://clusterfuzz.com/revisions?job=linux_msan_chrome&range=519805:519843
Fixed: https://clusterfuzz.com/revisions?job=linux_msan_chrome&range=523623:523651

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

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

Please try again now!

This was fixed by https://skia-review.googlesource.com/c/skia/+/83562.

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