CHECK failure: layout_snapped_paint_offset == snapped_paint_offset || subpixel_accumulation_may |
|||||
Issue descriptionDetailed report: https://clusterfuzz.com/testcase?key=5380580110499840 Fuzzer: marty_html_twiddler Job Type: linux_debug_chrome Platform Id: linux Crash Type: CHECK failure Crash Address: Crash State: layout_snapped_paint_offset == snapped_paint_offset || subpixel_accumulation_may blink::CompositingLayerPropertyUpdater::Update blink::PrePaintTreeWalk::WalkInternal Sanitizer: address (ASAN) Regressed: https://clusterfuzz.com/revisions?job=linux_debug_chrome&range=590577:590578 Reproducer Testcase: https://clusterfuzz.com/download?testcase_id=5380580110499840 Issue filed automatically. See https://github.com/google/clusterfuzz-tools for more information.
,
Sep 16
Automatically assigning owner based on suspected regression changelist https://chromium.googlesource.com/chromium/src/+/8661a7c51be77ca3e6a154e7fbade0b799eb6d9f ([Blink/BGPT+SPv2] Implement sticky position as transform node). 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.
,
Sep 17
I think it's a duplicate. This might be a better repro case, however.
,
Sep 17
,
Sep 25
ClusterFuzz has detected this issue as fixed in range 593713:593718. Detailed report: https://clusterfuzz.com/testcase?key=5380580110499840 Fuzzer: marty_html_twiddler Job Type: linux_debug_chrome Platform Id: linux Crash Type: CHECK failure Crash Address: Crash State: layout_snapped_paint_offset == snapped_paint_offset || subpixel_accumulation_may blink::CompositingLayerPropertyUpdater::Update blink::PrePaintTreeWalk::WalkInternal Sanitizer: address (ASAN) Regressed: https://clusterfuzz.com/revisions?job=linux_debug_chrome&range=590577:590578 Fixed: https://clusterfuzz.com/revisions?job=linux_debug_chrome&range=593713:593718 Reproducer Testcase: https://clusterfuzz.com/download?testcase_id=5380580110499840 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.
,
Sep 25
ClusterFuzz testcase 5380580110499840 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 |
|||||
Comment 1 by ClusterFuzz
, Sep 16Labels: Test-Predator-Auto-Components