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

Issue 854140 link

Starred by 1 user
Status: WontFix
Owner:
keishi@chromium.org
Closed: Nov 11
Cc:
█ brajkumar@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux
Pri: 2
Type: Bug



Sign in to add a comment

Data race in blink::SQLTransactionBackend::Trace

Project Member Reported by ClusterFuzz, Jun 19 2018 
Detailed report: https://clusterfuzz.com/testcase?key=6121563708194816

Fuzzer: inferno_twister
Job Type: linux_tsan_chrome_mp
Platform Id: linux

Crash Type: Data race READ 8
Crash Address: 0x7eef90cd2ee8
Crash State:
  blink::SQLTransactionBackend::Trace
  blink::TraceTrait<blink::SQLTransactionBackend>::Trace
  blink::ThreadHeap::AdvanceMarkingStackProcessing
  
Sanitizer: thread (TSAN)

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

Issue filed automatically.

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

Comment 1 by ClusterFuzz, Jun 19 2018

Components: Blink>MemoryAllocator>GarbageCollection
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.

Comment 2 by brajkumar@chromium.org, Jun 20 2018

Cc: brajkumar@chromium.org
Labels: M-68 Test-Predator-Wrong
Owner: keishi@chromium.org
Status: Assigned (was: Untriaged)
This issue looks similar to  bug 846144 , hence assigning to the same owner.

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

Thanks!
Project Member

Comment 3 by ClusterFuzz, Nov 11

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

Comment 4 by ClusterFuzz, Nov 11

Status: WontFix (was: Assigned)
ClusterFuzz testcase 6121563708194816 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