New issue
Advanced search Search tips

Issue 723379 link

Starred by 1 user

Issue metadata

Status: Verified
Owner: ----
Closed: May 2017
EstimatedDays: ----
NextAction: ----
OS: Linux
Pri: 1
Type: Bug



Sign in to add a comment

CHECK failure: frame_id_ != MSG_ROUTING_NONE in renderer_webaudiodevice_impl.cc

Project Member Reported by ClusterFuzz, May 17 2017

Issue description

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

Fuzzer: attekett_dom_fuzzer
Job Type: linux_msan_chrome
Platform Id: linux

Crash Type: CHECK failure
Crash Address: 
Crash State:
  frame_id_ != MSG_ROUTING_NONE in renderer_webaudiodevice_impl.cc
  content::RendererWebAudioDeviceImpl::RendererWebAudioDeviceImpl
  content::RendererWebAudioDeviceImpl::Create
  
Sanitizer: memory (MSAN)

Regressed: https://clusterfuzz.com/revisions?job=linux_msan_chrome&range=472186:472211

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


Issue filed automatically.

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

Comment 1 by ClusterFuzz, May 17 2017

ClusterFuzz has detected this issue as fixed in range 472221:472287.

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

Fuzzer: attekett_dom_fuzzer
Job Type: linux_msan_chrome
Platform Id: linux

Crash Type: CHECK failure
Crash Address: 
Crash State:
  frame_id_ != MSG_ROUTING_NONE in renderer_webaudiodevice_impl.cc
  content::RendererWebAudioDeviceImpl::RendererWebAudioDeviceImpl
  content::RendererWebAudioDeviceImpl::Create
  
Sanitizer: memory (MSAN)

Regressed: https://clusterfuzz.com/revisions?job=linux_msan_chrome&range=472186:472211
Fixed: https://clusterfuzz.com/revisions?job=linux_msan_chrome&range=472221:472287

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


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.
Project Member

Comment 2 by ClusterFuzz, May 17 2017

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

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

Sign in to add a comment