New issue
Advanced search Search tips

Issue 834550 link

Starred by 1 user

Issue metadata

Status: Verified
Owner:
Closed: Jul 21
Cc:
EstimatedDays: ----
NextAction: ----
OS: Linux
Pri: 1
Type: Bug



Sign in to add a comment

Timeout in content_security_policy_fuzzer

Project Member Reported by ClusterFuzz, Apr 19 2018

Issue description

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

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=510480:510512

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

Issue filed automatically.

See https://chromium.googlesource.com/chromium/src/+/master/testing/libfuzzer/reference.md for more information.
 
Cc: pnangunoori@chromium.org
Labels: M-67 Test-Predator-Wrong
Owner: infe...@chromium.org
Status: Assigned (was: Untriaged)
This issue seems to be similar to the  Issue 802133 .
inferno@ -- Could you please take a look into this issue.

Thanks!
Project Member

Comment 2 by ClusterFuzz, Jul 21

ClusterFuzz has detected this issue as fixed in range 576874:576881.

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

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=510480:510512
Fixed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_msan&range=576874:576881

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

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

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

Comment 3 by ClusterFuzz, Jul 21

Labels: ClusterFuzz-Verified
Status: Verified (was: Assigned)
ClusterFuzz testcase 6361087294046208 is verified as fixed, so closing issue as verified.

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

Sign in to add a comment