CHECK failure: layout_snapped_paint_offset == snapped_paint_offset || subpixel_accumulation_may |
||||
Issue descriptionDetailed report: https://clusterfuzz.com/testcase?key=5654524256321536 Fuzzer: ifratric-browserfuzzer-v3 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=5654524256321536 Issue filed automatically. See https://github.com/google/clusterfuzz-tools for more information.
,
Sep 30
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.
,
Oct 1
Same assert as https://bugs.chromium.org/p/chromium/issues/detail?id=816490, but has been marked as closed. So why are we still seeing this?
,
Oct 2
I can't reproduce it locally. Clusterfuzz seems also fail to reproduce the issue. The latest test stack trace crashed at "frame_sink_manager_impl.cc(62)] Check failed: sink_map_.empty()". It gave up minimization because of "Unable to reproduce crash reliably, skipping minimization (crashed 1/10)", and gave up regression job because of "Low confidence in regression range. Test case crashes in revision r583531 but not later revision r583547".
,
Oct 11
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/2902364fae7a4ae8a6225a643d2a5a3be89900d8 commit 2902364fae7a4ae8a6225a643d2a5a3be89900d8 Author: Xianzhu Wang <wangxianzhu@chromium.org> Date: Thu Oct 11 19:39:02 2018 Output more meaningful information on compositing layer paint offset mismatch Bug: 890598 Cq-Include-Trybots: luci.chromium.try:linux_layout_tests_slimming_paint_v2;master.tryserver.blink:linux_trusty_blink_rel Change-Id: I2aee8bf37891a163ce8182ef1c4e620eab5dcf2a Reviewed-on: https://chromium-review.googlesource.com/c/1276890 Reviewed-by: vmpstr <vmpstr@chromium.org> Commit-Queue: Xianzhu Wang <wangxianzhu@chromium.org> Cr-Commit-Position: refs/heads/master@{#598891} [modify] https://crrev.com/2902364fae7a4ae8a6225a643d2a5a3be89900d8/third_party/blink/renderer/core/paint/compositing/compositing_layer_property_updater.cc
,
Oct 12
With the #c5 CL, the DCHECK failure is:
[1:1:1012/004641.310970:FATAL:compositing_layer_property_updater.cc(57)] Check failed: layout_snapped_paint_offset == snapped_paint_offset ("7.98438,16" vs. "8,16")"LayoutBlockFlow METER"
|
||||
►
Sign in to add a comment |
||||
Comment 1 by ClusterFuzz
, Sep 30Labels: Test-Predator-Auto-Components