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

Issue 788497 link

Starred by 2 users
Status: Duplicate
Merged: issue 781618
Owner:
█ zijiehe@chromium.org
Last visit > 30 days ago
Closed: Nov 2017
Cc:
mbonadei@chromium.org
█ phoglund@chromium.org
kkaluri@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux
Pri: 2
Type: Bug



Sign in to add a comment

Data race in webrtc::XErrorTrap::XErrorTrap

Project Member Reported by ClusterFuzz, Nov 25 2017 
Detailed report: https://clusterfuzz.com/testcase?key=6723242164486144

Fuzzer: phoglund_webrtc_peerconnection
Job Type: linux_tsan_chrome_mp
Platform Id: linux

Crash Type: Data race WRITE 4
Crash Address: 0x7f4d00994ae0
Crash State:
  webrtc::XErrorTrap::XErrorTrap
  webrtc::GetWindowRect
  webrtc::XServerPixelBuffer::Init
  
Sanitizer: thread (TSAN)

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

Additional requirements: Requires HTTP

Issue filed automatically.

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

Note: This crash might not be reproducible with the provided testcase. That said, for the past 14 days we've been seeing this crash frequently. If you are unable to reproduce this, please try a speculative fix based on the crash stacktrace in the report. The fix can be verified by looking at the crash statistics in the report, a day after the fix is deployed. We will auto-close the bug if the crash is not seen for 14 days.
Project Member

Comment 1 by ClusterFuzz, Nov 25 2017

Labels: M-64 ClusterFuzz-Top-Crash ReleaseBlock-Beta
Testcase 6723242164486144 is a top crash on ClusterFuzz for linux platform. Please prioritize fixing this crash.

Marking this crash as a Beta release blocker.

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

Comment 2 by kkaluri@chromium.org, Nov 27 2017

Cc: kkaluri@chromium.org
Components: Blink>WebRTC
Labels: Test-Predator-Wrong
Owner: mbonadei@chromium.org
Status: Assigned (was: Untriaged)
Predator and CL could not provide any possible suspects.

Using the code search for the file, “x_error_trap.cc” assigning to concern owner.

Suspecting Commit# https://webrtc.git.corp.google.com/src.git/+/92ea95e34af5966555903026f45164afbd7e2088

mbonadei@ -- Could you please look into this issue, kindly reassign if it has nothing to do with your changes.


Thank You...

Comment 3 by mbonadei@chromium.org, Nov 27 2017

Cc: mbonadei@chromium.org phoglund@chromium.org
Owner: zijiehe@chromium.org
zijiehe@, can you look into this report? Sounds like a a data race in desktop_capture.

Comment 4 by ajha@chromium.org, Nov 28 2017 

M-64 will be branched in 2 days time, so please plan the fix accordingly. Would be good to have all the Beta blockers resolved before branch point.

Comment 5 by ajha@chromium.org, Nov 30 2017 

Friendly ping for an update.

Comment 6 by zijiehe@chromium.org, Nov 30 2017

Mergedinto: 781618
Status: Duplicate (was: Assigned)
This bug duplicates with  bug 781618 .
►

Sign in to add a comment