New issue
Advanced search Search tips

Issue 798054 link

Starred by 1 user

Issue metadata

Status: Verified
Owner:
Closed: Jan 2018
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux , Windows
Pri: 1
Type: Bug



Sign in to add a comment

Null-dereference READ in blink::ObjectPaintPropertyTreeBuilder::UpdateForSelf

Project Member Reported by ClusterFuzz, Dec 29 2017

Issue description

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

Fuzzer: ochang_domfuzzer
Job Type: windows_asan_content_shell
Platform Id: windows

Crash Type: Null-dereference READ
Crash Address: 0x000000000018
Crash State:
  blink::ObjectPaintPropertyTreeBuilder::UpdateForSelf
  blink::PrePaintTreeWalk::WalkInternal
  blink::PrePaintTreeWalk::Walk
  
Sanitizer: address (ASAN)

Regressed: https://clusterfuzz.com/revisions?job=windows_asan_content_shell&range=525576:525595

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

Issue filed automatically.

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

Comment 1 by ClusterFuzz, Dec 29 2017

Labels: OS-Linux
Project Member

Comment 2 by ClusterFuzz, Dec 29 2017

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 3 by ClusterFuzz, Dec 29 2017

Labels: Test-Predator-Auto-Owner
Owner: wangxianzhu@chromium.org
Status: Assigned (was: Untriaged)
Automatically assigning owner based on suspected regression changelist https://chromium.googlesource.com/chromium/src/+/a6bdae9e35c62c9c0526cc2078f3b59e53ea4fa7 ([SPv175+] Fix some multi-fragment paint offset issues).

If this is incorrect, please remove the owner and apply the Test-Predator-Wrong-CLs label.
Project Member

Comment 4 by bugdroid1@chromium.org, Jan 3 2018

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

commit 55c7f6aa2c7733b8d104d16a3934b1e9eabe2180
Author: Xianzhu Wang <wangxianzhu@chromium.org>
Date: Wed Jan 03 20:54:49 2018

[PE] Fix crash when handling multicol composited iframe

Bug:  798054 
Cq-Include-Trybots: master.tryserver.blink:linux_trusty_blink_rel;master.tryserver.chromium.linux:linux_layout_tests_slimming_paint_v2
Change-Id: I90888e88e6d3487a754967eebf89c2fffcadf3eb
Reviewed-on: https://chromium-review.googlesource.com/847693
Reviewed-by: Chris Harrelson <chrishtr@chromium.org>
Commit-Queue: Xianzhu Wang <wangxianzhu@chromium.org>
Cr-Commit-Position: refs/heads/master@{#526802}
[modify] https://crrev.com/55c7f6aa2c7733b8d104d16a3934b1e9eabe2180/third_party/WebKit/Source/core/paint/PaintPropertyTreeBuilder.cpp
[modify] https://crrev.com/55c7f6aa2c7733b8d104d16a3934b1e9eabe2180/third_party/WebKit/Source/core/paint/PaintPropertyTreeBuilderTest.cpp

Project Member

Comment 5 by ClusterFuzz, Jan 4 2018

ClusterFuzz has detected this issue as fixed in range 526787:526806.

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

Fuzzer: ochang_domfuzzer
Job Type: windows_asan_content_shell
Platform Id: windows

Crash Type: Null-dereference READ
Crash Address: 0x000000000018
Crash State:
  blink::ObjectPaintPropertyTreeBuilder::UpdateForSelf
  blink::PrePaintTreeWalk::WalkInternal
  blink::PrePaintTreeWalk::Walk
  
Sanitizer: address (ASAN)

Regressed: https://clusterfuzz.com/revisions?job=windows_asan_content_shell&range=525576:525595
Fixed: https://clusterfuzz.com/revisions?job=windows_asan_content_shell&range=526787:526806

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

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 6 by ClusterFuzz, Jan 4 2018

Labels: ClusterFuzz-Verified
Status: Verified (was: Assigned)
ClusterFuzz testcase 4852850764283904 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