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

Issue 914156 link

Starred by 1 user
Status: WontFix
Owner:
█ gmx@chromium.org
Last visit 20 days ago
Closed: Dec 29
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux
Pri: 2
Type: Bug



Sign in to add a comment

Data race in libgtk-3.so.0

Project Member Reported by ClusterFuzz, Dec 12 
Detailed report: https://clusterfuzz.com/testcase?key=6609482177839104

Fuzzer: attekett_surku_fuzzer
Job Type: linux_tsan_chrome_mp
Platform Id: linux

Crash Type: Data race READ 8
Crash Address: 0x7b10000d87c0
Crash State:
  libgtk-3.so.0
  g_malloc
  base::MessageLoopImpl::Run
  
Sanitizer: thread (TSAN)

Regressed: https://clusterfuzz.com/revisions?job=linux_tsan_chrome_mp&range=615631:615632

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

Additional requirements: Requires Gestures

Issue filed automatically.

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

Comment 1 by ClusterFuzz, Dec 12

Components: 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, Dec 12

Labels: Test-Predator-Auto-Owner
Owner: gmx@chromium.org
Status: Assigned (was: Untriaged)
Automatically assigning owner based on suspected regression changelist https://chromium.googlesource.com/chromium/src/+/f4728fa7e63e608a59684c6a3cadf43138f961e8 (PerfProvider: Add a main profile provider class for Chrome OS).

If this is incorrect, please let us know why and apply the Test-Predator-Wrong-CLs label. If you aren't the correct owner for this issue, please unassign yourself as soon as possible so it can be re-triaged.
Project Member

Comment 3 by ClusterFuzz, Dec 16

Labels: -Reproducible Unreproducible
ClusterFuzz testcase 6609482177839104 appears to be flaky, updating reproducibility label.
Project Member

Comment 4 by ClusterFuzz, Dec 29

Status: WontFix (was: Assigned)
ClusterFuzz testcase 6609482177839104 is flaky and no longer crashes, so closing issue.

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

Sign in to add a comment