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

Issue 829543 link

Starred by 1 user
Status: Duplicate
Merged: issue 794920
Owner:
rsesek@chromium.org
Closed: Apr 2018
Cc:
mfo...@chromium.org
ifratric@google.com
█ roc...@chromium.org
█ brajkumar@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux
Pri: 2
Type: Bug



Sign in to add a comment

Data race in strncpy

Project Member Reported by ClusterFuzz, Apr 5 2018 
Detailed report: https://clusterfuzz.com/testcase?key=5662469020975104

Fuzzer: ifratric-browserfuzzer-v3
Job Type: linux_tsan_chrome_mp
Platform Id: linux

Crash Type: Data race WRITE 8
Crash Address: 0x7bb400002050
Crash State:
  strncpy
  crash_reporter::internal::CrashKeyStringImpl::Set
  ChromeContentClient::SetActiveURL
  
Sanitizer: thread (TSAN)

Regressed: https://clusterfuzz.com/revisions?job=linux_tsan_chrome_mp&range=546382:546390

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

Issue filed automatically.

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

Comment 1 by ClusterFuzz, Apr 5 2018

Components: Internals>CrashReporting
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 5 2018

Cc: mfo...@chromium.org roc...@chromium.org
Labels: Test-Predator-Auto-CC
Automatically adding ccs based on suspected regression changelists:

Mojo Bindings: SequenceLocalSyncEventWatcher by rockot@chromium.org - https://chromium.googlesource.com/chromium/src/+/aa20dccb4efb759eb5148433441acaad123e80de

Reland "[chrome.dial] Remove chrome.dial." by mfoltz@chromium.org - https://chromium.googlesource.com/chromium/src/+/1c4a4beaf3feb5f0e9b16b2e71aa1065c4d6c28c

If this is incorrect, please let us know why and apply the Test-Predator-Wrong-CLs label.

Comment 3 by roc...@chromium.org, Apr 5 2018

Labels: Test-Predator-Wrong-CLs
I have serious doubts about either of these CLs being responsible.

Looks like a data race in crash keys stuff. Neither of the CLs mess with crash keys.

Comment 4 by brajkumar@chromium.org, Apr 6 2018

Cc: brajkumar@chromium.org
Owner: rsesek@chromium.org
Status: Assigned (was: Untriaged)
> Unable to find actual suspect through code search and also observing no CL's under regression range.

> By comparing the stack trace of this issue, it looks similar to   bug 797830  , hence assigning to the same owner for more updates.

> rsesek@ Could you please take a look in to this issue?

Thanks!

Comment 5 by rsesek@chromium.org, Apr 6 2018

Mergedinto: 794920
Status: Duplicate (was: Assigned)
►

Sign in to add a comment