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

Issue 836290 link

Starred by 2 users

Issue metadata

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



Sign in to add a comment

Data race in gtk_query_matches_string

Project Member Reported by ClusterFuzz, Apr 24 2018

Issue description

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

Fuzzer: attekett_surku_fuzzer
Job Type: linux_tsan_chrome_mp
Platform Id: linux

Crash Type: Data race READ 1
Crash Address: 0x7b0400031aa0
Crash State:
  gtk_query_matches_string
  base::MessageLoop::Run
  base::RunLoop::Run
  
Sanitizer: thread (TSAN)

Regressed: https://clusterfuzz.com/revisions?job=linux_tsan_chrome_mp&range=523888:523922

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

Issue filed automatically.

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

Comment 1 by ClusterFuzz, Apr 24 2018

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, Apr 24 2018

Labels: Test-Predator-Auto-Owner
Owner: timbrown@chromium.org
Status: Assigned (was: Untriaged)
Automatically assigning owner based on suspected regression changelist https://chromium.googlesource.com/chromium/src/+/c1829894ac62e37257973d5e5c27d1bffb9888b3 (Remove remaining references to gconf).

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.
Cc: timbrown@chromium.org
Labels: Test-Predator-Wrong-CLs
Owner: ----
Status: Unconfirmed (was: Assigned)
The suspected CL is a nop. It's mostly comment changes. Other than that, it removes two files which are dead code, and removes an entry from a mojo enum. The enum has since been removed, so it is very very unlikely that it is the cause of the issue.

Note that this CL has been blamed several times for issues which apparently are not reproducible. It really looks like there is something else going on.

Sign in to add a comment