New issue
Advanced search Search tips

Issue 702859 link

Starred by 0 users

Issue metadata

Status: Verified
Owner: ----
Closed: Mar 2017
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux
Pri: 2
Type: Bug



Sign in to add a comment

Data race in blink::ThreadState::scheduleV8FollowupGCIfNeeded

Project Member Reported by ClusterFuzz, Mar 18 2017

Issue description

Comment 1 by sigbjo...@opera.com, Mar 18 2017

Components: Blink>MemoryAllocator>GarbageCollection
Project Member

Comment 2 by ClusterFuzz, Mar 18 2017

ClusterFuzz has detected this issue as fixed in range 457767:457787.

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

Fuzzer: phoglund_webrtc_peerconnection
Job Type: linux_tsan_chrome_mp
Platform Id: linux

Crash Type: Data race READ 8
Crash Address: 0x7fa099aa5428
Crash State:
  blink::ThreadState::scheduleV8FollowupGCIfNeeded
  blink::V8GCController::gcEpilogue
  v8::internal::Heap::CallGCEpilogueCallbacks
  
Sanitizer: thread (TSAN)

Regressed: https://clusterfuzz.com/revisions?job=linux_tsan_chrome_mp&range=457748:457757
Fixed: https://clusterfuzz.com/revisions?job=linux_tsan_chrome_mp&range=457767:457787

Reproducer Testcase: https://clusterfuzz.com/download/AMIfv948DSV8LyExx7FLqeJmMM4Rv4dS_m4-swwLfu3Z96KiscwKZtf86jgWA07vKG38H89qD1x89RkL0GFQXlLlmykYr9TIy1k__Ak8BiekN7-iGWyqR_mtuhlTyXfOA2OQuljqPnPvLkCG1oDA6I7_0r55zDRwmUDruzHtiSRgigf0nDvlxVbmk0wkPAhYJCHZFg_rNPobaAyPB8gSbOEaqpNkI05vSYam1Eb1G9rvM6D6kx3OkjmEEiFojZGLUNwkTxF7zW-80raOhypauSzEMod2u6tkJzQ0XVN39w2_Q5RW0KH4CEJ0GqH3m6ZJ3djDNE2mVXg42mserO8638hiHJDjrdHc4s6fzs387UCB9ib0sW6E7NXYdF2Q-_ezf1RXT7LFnigX0sRadA_K7qBJaeUWMTT9Ww?testcase_id=5107158913122304


Additional requirements: Requires HTTP

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 3 by ClusterFuzz, Mar 18 2017

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