New issue
Advanced search Search tips
Note: Color blocks (like █ or █) mean that a user may not be available. Tooltip shows the reason.

Issue 739957 link

Starred by 3 users
Status: Verified
Owner:
█ alokp@chromium.org
Last visit > 30 days ago
Closed: Jul 2017
Cc:
█ msrchandra@chromium.org
EstimatedDays: ----
NextAction: ----
OS: Linux
Pri: 2
Type: Bug



Sign in to add a comment

Data race in pthread_mutex_lock

Project Member Reported by ClusterFuzz, Jul 6 2017 
Detailed report: https://clusterfuzz.com/testcase?key=5155761230708736

Fuzzer: phoglund_webrtc_peerconnection
Job Type: linux_tsan_chrome_mp
Platform Id: linux

Crash Type: Data race ATOMIC READ 1
Crash Address: 0x7b0c0004a7f0
Crash State:
  pthread_mutex_lock
  pa_mutex_lock
  media::pulse::InitPulse
  
Sanitizer: thread (TSAN)

Regressed: https://clusterfuzz.com/revisions?job=linux_tsan_chrome_mp&range=484617:484635

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


Additional requirements: Requires HTTP

Issue filed automatically.

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

Comment 1 by msrchandra@chromium.org, Jul 10 2017

Cc: msrchandra@chromium.org
Labels: Test-Predator-Wrong-CLs
Owner: alokp@chromium.org
Status: Assigned (was: Untriaged)
Predator and CL did not provide any possible suspects.
Using Code Search for the file, "pulse_util.h" assigning to the concern owner.
Suspecting Commit#
https://chromium.googlesource.com/chromium/src/+/2cbd4fcab300af5aa4ef76752673901d58da0f24

@alokp -- Could you please look into the issue, kindly re-assign if this is not related to your changes.
Thank You.

Comment 2 by msrchandra@chromium.org, Jul 11 2017 

 Issue 740903  has been merged into this issue.
Project Member

Comment 3 by ClusterFuzz, Jul 12 2017

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