New issue
Advanced search Search tips

Issue 842495 link

Starred by 3 users

Issue metadata

Status: Verified
Owner:
Closed: May 2018
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux
Pri: 1
Type: Bug



Sign in to add a comment

Null-dereference READ in blink::PaintLayer::GetLayoutBox

Project Member Reported by ClusterFuzz, May 13 2018

Issue description

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

Fuzzer: inferno_webbot
Job Type: linux_ubsan_chrome
Platform Id: linux

Crash Type: Null-dereference READ
Crash Address: 0x000000000010
Crash State:
  blink::PaintLayer::GetLayoutBox
  GetLayoutBox
  blink::PaintLayerScrollableArea::UpdateScrollDimensions
  
Sanitizer: undefined (UBSAN)

Regressed: https://clusterfuzz.com/revisions?job=linux_ubsan_chrome&range=537047:537050

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

Issue filed automatically.

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

Comment 1 by ClusterFuzz, May 13 2018

Components: Blink>Paint
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, May 13 2018

Labels: Test-Predator-Auto-Owner
Owner: flackr@chromium.org
Status: Assigned (was: Untriaged)
Automatically assigning owner based on suspected regression changelist https://chromium.googlesource.com/chromium/src/+/3ab971569afab25c6e330b3898fba29288b68732 (Use PaintLayer pointer from PaintLayerScrollableArea as PaintLayer is destructed first.).

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.

Comment 3 by flackr@chromium.org, May 29 2018

Status: Started (was: Assigned)
CL is up:
https://chromium-review.googlesource.com/c/chromium/src/+/1075826

Comment 4 by flackr@chromium.org, May 29 2018

Components: -Blink>Paint Blink>Scroll
Project Member

Comment 5 by bugdroid1@chromium.org, May 29 2018

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/a0ec0ab14e337fa5a41652551eeb7a098d5fe484

commit a0ec0ab14e337fa5a41652551eeb7a098d5fe484
Author: Robert Flack <flackr@chromium.org>
Date: Tue May 29 18:31:11 2018

Ignore delayed scroll offset clamp if PLSA was destroyed.

Bug:  842495 
Cq-Include-Trybots: master.tryserver.blink:linux_trusty_blink_rel;master.tryserver.chromium.linux:linux_layout_tests_slimming_paint_v2
Change-Id: I41b3a973a2f9aa36e245e4cfbe1ad8f0de4b5ad8
Reviewed-on: https://chromium-review.googlesource.com/1075826
Commit-Queue: Robert Flack <flackr@chromium.org>
Reviewed-by: David Bokan <bokan@chromium.org>
Cr-Commit-Position: refs/heads/master@{#562516}
[modify] https://crrev.com/a0ec0ab14e337fa5a41652551eeb7a098d5fe484/third_party/blink/renderer/core/paint/paint_layer_scrollable_area.cc
[modify] https://crrev.com/a0ec0ab14e337fa5a41652551eeb7a098d5fe484/third_party/blink/renderer/core/paint/paint_layer_scrollable_area.h
[modify] https://crrev.com/a0ec0ab14e337fa5a41652551eeb7a098d5fe484/third_party/blink/renderer/core/paint/paint_layer_scrollable_area_test.cc

Project Member

Comment 6 by ClusterFuzz, May 30 2018

ClusterFuzz has detected this issue as fixed in range 562513:562517.

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

Fuzzer: inferno_webbot
Job Type: linux_ubsan_chrome
Platform Id: linux

Crash Type: Null-dereference READ
Crash Address: 0x000000000010
Crash State:
  blink::PaintLayer::GetLayoutBox
  GetLayoutBox
  blink::PaintLayerScrollableArea::UpdateScrollDimensions
  
Sanitizer: undefined (UBSAN)

Regressed: https://clusterfuzz.com/revisions?job=linux_ubsan_chrome&range=537047:537050
Fixed: https://clusterfuzz.com/revisions?job=linux_ubsan_chrome&range=562513:562517

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

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.
Project Member

Comment 7 by ClusterFuzz, May 30 2018

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

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

Sign in to add a comment