New issue
Advanced search Search tips

Issue 837138 link

Starred by 1 user

Issue metadata

Status: Verified
Owner: ----
Closed: Apr 2018
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux
Pri: 2
Type: Bug



Sign in to add a comment

Data race in media::AudioOutputDevice::AudioThreadCallback::Process

Project Member Reported by ClusterFuzz, Apr 26 2018

Issue description

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

Fuzzer: inferno_flicker
Job Type: linux_tsan_chrome_mp
Platform Id: linux

Crash Type: Data race READ 1
Crash Address: 0x7b4000000ad8
Crash State:
  media::AudioOutputDevice::AudioThreadCallback::Process
  media::AudioDeviceThread::ThreadMain
  base::ThreadFunc
  
Sanitizer: thread (TSAN)

Regressed: https://clusterfuzz.com/revisions?job=linux_tsan_chrome_mp&range=553827:553833

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

Issue filed automatically.

See https://github.com/google/clusterfuzz-tools for more information.
 
Project Member

Comment 1 by ClusterFuzz, Apr 26 2018

Components: Blink>Media>Audio Internals>Core
Labels: Test-Predator-Auto-Components
Automatically applying components based on crash stacktrace and information from OWNERS files.

If this is incorrect, please apply the Test-Predator-Wrong-Components label.
Project Member

Comment 2 by ClusterFuzz, Apr 27 2018

ClusterFuzz has detected this issue as fixed in range 553963:553965.

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

Fuzzer: inferno_flicker
Job Type: linux_tsan_chrome_mp
Platform Id: linux

Crash Type: Data race READ 1
Crash Address: 0x7b4000000ad8
Crash State:
  media::AudioOutputDevice::AudioThreadCallback::Process
  media::AudioDeviceThread::ThreadMain
  base::ThreadFunc
  
Sanitizer: thread (TSAN)

Regressed: https://clusterfuzz.com/revisions?job=linux_tsan_chrome_mp&range=553827:553833
Fixed: https://clusterfuzz.com/revisions?job=linux_tsan_chrome_mp&range=553963:553965

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

See https://github.com/google/clusterfuzz-tools 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, Apr 27 2018

Labels: ClusterFuzz-Verified
Status: Verified (was: Untriaged)
ClusterFuzz testcase 5773648796057600 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