Suspected CL could 
https://chromium.googlesource.com/chromium/src/+/1f4996786dd7ab2e5d7f51c72f9309ee50aeb176%5E%21/media/audio/audio_manager.cc

Last updated by alokp @ weeks ago , please have a look and reassign if needed.

Thank you.

ClusterFuzz has detected this issue as fixed in range 398017:398351.

Detailed report: https://cluster-fuzz.appspot.com/testcase?key=6547348813774848

Fuzzer: inferno_layout_test_unmodified
Job Type: linux_asan_content_shell_drt
Platform Id: linux

Crash Type: UNKNOWN READ
Crash Address: 0x000000000000
Crash State:
  blink::ScriptState::from
  blink::messageHandlerInMainThread
  v8::internal::MessageHandler::ReportMessage
  
Fixed: https://cluster-fuzz.appspot.com/revisions?job=linux_asan_content_shell_drt&range=398017:398351

Minimized Testcase (0.30 Kb): https://cluster-fuzz.appspot.com/download/AMIfv97NyVJOuQhsAqVig0S2hkEyWSaT8bqXnM58tlleXUN3CRmpCEdh5_suJNGsd91nQHD902_iFjj_yGszLgN6_ajM97gbYpMRs-JaNB5ZVr-1iBLSg5BW1JnoeKsfmjG61Pe5V19TZAE9PzBKqhaT8g8tiToSeA?testcase_id=6547348813774848

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.

The testcase is not accessible to me. The crash state points to blink which runs in the renderer process. The patch referenced in comment #1 only touches code running in the browser process.

mmohammad@: Can you explain why do you think this bug is caused by r388211? Is there something in the test case or callstack elsewhere that I am missing?

This file audio_manager.cc Last updated by you, so assigned 

And as I mentioned in my last comment, this is a blink issue not AudioManager. I think you should look for changes in third_party/Webkit.

Detailed report: https://cluster-fuzz.appspot.com/testcase?key=6055593379102720

Fuzzer: inferno_layout_test_unmodified
Job Type: linux_lsan_chrome_mp
Platform Id: linux

Crash Type: UNKNOWN READ
Crash Address: 0x000000000000
Crash State:
  blink::ScriptState::from
  blink::messageHandlerInMainThread
  v8::internal::MessageHandler::ReportMessage
  
Regressed: https://cluster-fuzz.appspot.com/revisions?job=linux_lsan_chrome_mp&range=388139:388170
Fixed: https://cluster-fuzz.appspot.com/revisions?job=linux_lsan_chrome_mp&range=398017:398351

Minimized Testcase (0.33 Kb): https://cluster-fuzz.appspot.com/download/AMIfv95gzbFqHFxXTrmrmZMl0a3hZbhr3Z02cz-g5q0FpUVw6sifPNe2cAZ95obbHLIIMFlbnj-3DvPC2Qy4rNH9d2yEW1NCfMF1S4l61IbkHz0RSF6slO5Hpzy6ns96Mnjucg_jv6yKj0-3_N6v0H_gwcVfTDemdQ?testcase_id=6055593379102720

Filer: tkonchada

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

Detailed report: https://cluster-fuzz.appspot.com/testcase?key=5901687856562176

Fuzzer: inferno_layout_test_unmodified
Job Type: linux_asan_content_shell_drt
Platform Id: linux

Crash Type: UNKNOWN READ
Crash Address: 0x000000000000
Crash State:
  blink::ScriptState::from
  blink::messageHandlerInMainThread
  v8::internal::MessageHandler::ReportMessage
  

Minimized Testcase (0.30 Kb): https://cluster-fuzz.appspot.com/download/AMIfv971HKQzklbE91C1k3ZqmSElPR2ugvbCg_KBGhL1Gc7X44SfbqgdJ1lQBu-QLLejoNceZH6rbQk6FzHWAkaJPa09AEjW91mxkQON9dyTm4YRtuotOycAtVKuTTvUOlYEF19tMsy4E7tEC-rQtUW3dqDKcRRvsA?testcase_id=5901687856562176

Filer: mmohammad

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

ClusterFuzz has detected this issue as fixed in range 398017:398351.

Detailed report: https://cluster-fuzz.appspot.com/testcase?key=5901687856562176

Fuzzer: inferno_layout_test_unmodified
Job Type: linux_asan_content_shell_drt
Platform Id: linux

Crash Type: UNKNOWN READ
Crash Address: 0x000000000000
Crash State:
  blink::ScriptState::from
  blink::messageHandlerInMainThread
  v8::internal::MessageHandler::ReportMessage
  
Fixed: https://cluster-fuzz.appspot.com/revisions?job=linux_asan_content_shell_drt&range=398017:398351

Minimized Testcase (0.30 Kb): https://cluster-fuzz.appspot.com/download/AMIfv971HKQzklbE91C1k3ZqmSElPR2ugvbCg_KBGhL1Gc7X44SfbqgdJ1lQBu-QLLejoNceZH6rbQk6FzHWAkaJPa09AEjW91mxkQON9dyTm4YRtuotOycAtVKuTTvUOlYEF19tMsy4E7tEC-rQtUW3dqDKcRRvsA?testcase_id=5901687856562176

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.

ClusterFuzz testcase is verified as fixed, closing issue.

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

Removing EditIssue view restrictions from ClusterFuzz filed bugs. If you believe that this issue should still be restricted, please reapply the label.

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