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

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

ClusterFuzz is analyzing your testcase. Developers can follow the progress at https://cluster-fuzz.appspot.com/testcase?key=4921320838266880

Rodolph, can you take a look at this one?

Can you give me access to the cluster-fuzz pages (report, test case, analyse)?

Here is the test case.

Deleted: testcase-643001.js 1.3 KB

testcase-643001.js 1.3 KB View Download

I cannot reproduce this bug.

ClusterFuzz has detected this issue as fixed in range 469332:469344.

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

Fuzzer: mbarbella_js_mutation
Job Type: linux_msan_d8
Platform Id: linux

Crash Type: Use-of-uninitialized-value
Crash Address: 
Crash State:
  v8::internal::Simulator::VisitCompareBranch
  v8::internal::Simulator::CallVoid
  v8::internal::Simulator::CallJS
  
Sanitizer: memory (MSAN)

Recommended Security Severity: Medium

Regressed: https://clusterfuzz.com/revisions?job=linux_msan_d8&range=413682:413688
Fixed: https://clusterfuzz.com/revisions?job=linux_msan_d8&range=469332:469344

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


See https://dev.chromium.org/Home/chromium-security/bugs/reproducing-clusterfuzz-bugs for more information.

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