New issue
Advanced search Search tips

Issue 907944 link

Starred by 3 users

Issue metadata

Status: Untriaged
Owner: ----
Cc:
EstimatedDays: ----
NextAction: ----
OS: Linux
Pri: 2
Type: Bug



Sign in to add a comment

Data race in g_closure_unref

Project Member Reported by ClusterFuzz, Nov 22

Issue description

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

Fuzzer: attekett_surku_fuzzer
Job Type: linux_tsan_chrome_mp
Platform Id: linux

Crash Type: Data race WRITE 8
Crash Address: 0x7b040005a4a0
Crash State:
  g_closure_unref
  
Sanitizer: thread (TSAN)

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

Issue filed automatically.

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

Comment 1 by ClusterFuzz, Nov 24

Labels: Fuzz-Blocker ReleaseBlock-Beta M-72
This crash occurs very frequently on linux platform and is likely preventing the fuzzer attekett_surku_fuzzer from making much progress. Fixing this will allow more bugs to be found.

Marking this bug as a blocker for next Beta release.

If this is incorrect, please add ClusterFuzz-Wrong label and remove the ReleaseBlock-Beta label.
Labels: Test-Predator-Wrong CF-NeedsTriage
Unable to find actual suspect through code search and also observing no CL's under regression range, hence adding appropriate label and requesting someone from dev team to look in to this issue.

Thanks!
Cc: thomasanderson@chromium.org
Labels: -CF-NeedsTriage
thomasanderson@, just wondering do you have any inputs here?
thomasanderson@ Have you had a chance to review this. Please update the bug if it is not a blocker for beta release.
Labels: -ReleaseBlock-Beta -M-72 M-71 ClusterFuzz-Wrong
As per the latest CF report (https://clusterfuzz.com/testcase-detail/4962873107021824) it's not impacting M72. So removing the blocker label.

Sign in to add a comment