New issue
Advanced search Search tips

Issue 771504 link

Starred by 1 user

Issue metadata

Status: Verified
Owner: ----
Closed: Oct 2017
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux
Pri: 2
Type: Bug



Sign in to add a comment

Data race in blink::Gradient::ApplyToFlags

Project Member Reported by ClusterFuzz, Oct 4 2017

Issue description

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

Fuzzer: attekett_surku_fuzzer
Job Type: linux_tsan_chrome_mp
Platform Id: linux

Crash Type: Data race READ 8
Crash Address: 0x7b4800073850
Crash State:
  blink::Gradient::ApplyToFlags
  blink::SVGPaintServer::ApplyToPaintFlags
  blink::SVGPaintContext::PaintForLayoutObject
  
Sanitizer: thread (TSAN)

Regressed: https://clusterfuzz.com/revisions?job=linux_tsan_chrome_mp&range=505537:505540

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

Issue filed automatically.

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

Comment 1 by ClusterFuzz, Oct 4 2017

Components: Blink>SVG Internals>Compositing
Labels: Test-Predator-AutoComponents
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, Oct 4 2017

ClusterFuzz has detected this issue as fixed in range 506280:506290.

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

Fuzzer: attekett_surku_fuzzer
Job Type: linux_tsan_chrome_mp
Platform Id: linux

Crash Type: Data race READ 8
Crash Address: 0x7b4800073850
Crash State:
  blink::Gradient::ApplyToFlags
  blink::SVGPaintServer::ApplyToPaintFlags
  blink::SVGPaintContext::PaintForLayoutObject
  
Sanitizer: thread (TSAN)

Regressed: https://clusterfuzz.com/revisions?job=linux_tsan_chrome_mp&range=505537:505540
Fixed: https://clusterfuzz.com/revisions?job=linux_tsan_chrome_mp&range=506280:506290

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

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

If you suspect that the result above is incorrect, try re-doing that job on the test case report page.

Comment 3 by f...@opera.com, Oct 4 2017

Cc: khushals...@chromium.org
Status: Fixed (was: Untriaged)
Probably caused by 53b8ed642644f245e3cb8d5cf2541bf3778ae7de (and subsequently fixed by f77a3ffbb03b2037f2b752ca638a101187f106f0)

(CC:ing author in case this sheds some light on the underlying issue.)
Project Member

Comment 4 by ClusterFuzz, Oct 4 2017

Labels: ClusterFuzz-Verified
Status: Verified (was: Fixed)
ClusterFuzz testcase 4854760539947008 is verified as fixed, so closing issue as verified.

If this is incorrect, please add ClusterFuzz-Wrong label and re-open the issue.
Labels: -Test-Predator-AutoComponents Test-Predator-Auto-Components

Sign in to add a comment