New issue
Advanced search Search tips

Issue 874432 link

Starred by 1 user
Status: Assigned
Owner:
vogelheim@chromium.org
EstimatedDays: ----
NextAction: ----
OS: Linux , Windows , Chrome
Pri: 1
Type: Bug



Sign in to add a comment

Timeout in content_security_policy_fuzzer

Project Member Reported by ClusterFuzz, Aug 15 
Detailed report: https://clusterfuzz.com/testcase?key=6018052790157312

Fuzzer: libFuzzer_content_security_policy_fuzzer
Job Type: libfuzzer_chrome_msan
Platform Id: linux

Crash Type: Timeout (exceeds 25 secs)
Crash Address: 
Crash State:
  content_security_policy_fuzzer
  
Sanitizer: memory (MSAN)

Regressed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_msan&range=576874:576881

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

Issue filed automatically.

See https://chromium.googlesource.com/chromium/src/+/master/testing/libfuzzer/reference.md for more information.
Project Member

Comment 1 by ClusterFuzz, Aug 15

Labels: Test-Predator-Auto-Owner
Owner: vogelheim@chromium.org
Status: Assigned (was: Untriaged)
Automatically assigning owner based on suspected regression changelist https://chromium.googlesource.com/chromium/src/+/80c658c16ee9238f6dbbd72a40837def39659f85 (Origin Policy: Apply CSP of an active origin policy.).

If this is incorrect, please let us know why and apply the Test-Predator-Wrong-CLs label. If you aren't the correct owner for this issue, please unassign yourself as soon as possible so it can be re-triaged.
Project Member

Comment 2 by ClusterFuzz, Oct 9

Labels: OS-Windows
Project Member

Comment 3 by ClusterFuzz, Dec 1

Labels: -Reproducible Unreproducible
ClusterFuzz testcase 6018052790157312 appears to be flaky, updating reproducibility label.

Comment 4 by infe...@chromium.org, Dec 1

Labels: -Unreproducible Reproducible
Please ignore the last comment about testcase being unreproducible. The testcase is still reproducible. This happened due to a code refactoring on ClusterFuzz side, and the underlying root cause is now fixed. Resetting the label back to Reproducible. Sorry about the inconvenience caused from these incorrect notifications.

Comment 5 by infe...@chromium.org, Dec 1

Labels: -Unreproducible Reproducible
Please ignore the last comment about testcase being unreproducible. The testcase is still reproducible. This happened due to a code refactoring on ClusterFuzz side, and the underlying root cause is now fixed. Resetting the label back to Reproducible. Sorry about the inconvenience caused from these incorrect notifications.
Project Member

Comment 6 by ClusterFuzz, Dec 6

Labels: OS-Chrome
►

Sign in to add a comment