New issue
Advanced search Search tips

Issue 825742 link

Starred by 1 user

Issue metadata

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



Sign in to add a comment

CHECK failure: layout_object_mapped_result.EqualWithinEpsilon(result.BoundingBox(), 0.1f) || la

Project Member Reported by ClusterFuzz, Mar 26 2018

Issue description

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

Fuzzer: marty_html_twiddler
Job Type: linux_debug_chrome
Platform Id: linux

Crash Type: CHECK failure
Crash Address: 
Crash State:
  layout_object_mapped_result.EqualWithinEpsilon(result.BoundingBox(), 0.1f) || la
  blink::LayoutGeometryMap::MapToAncestor
  blink::LayoutGeometryMap::AbsoluteRect
  
Sanitizer: address (ASAN)

Regressed: https://clusterfuzz.com/revisions?job=linux_debug_chrome&range=529050:529051

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

Issue filed automatically.

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

Comment 1 by ClusterFuzz, Mar 26 2018

Components: Blink>Compositing Blink>Layout
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, Mar 26 2018

Labels: Test-Predator-Auto-Owner
Owner: lukasza@chromium.org
Status: Assigned (was: Untriaged)
Automatically assigning owner based on suspected regression changelist https://chromium.googlesource.com/chromium/src/+/ffb5de3934abd4e16399b2f79e7100823c6076fd (Don't propagate cmdline flags that are not read by renderer processes.).

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.
Cc: vmp...@chromium.org
Labels: Test-Predator-Wrong-CLs
Owner: chrishtr@chromium.org
chrishtr@ - could you PTAL and help triage further (you've touched the failing DCHECK relatively recently in r535606).  Also +vmpstr@ who was also tweaking the DCHECK in r531977.

I am adding Test-Predator-Wrong-CLs label and removing myself as an owner, because I think the explanation from  https://crbug.com/823148#c3  applies here as well.
Project Member

Comment 4 by bugdroid1@chromium.org, Mar 31 2018

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

commit 91356a30f3c3df37ecd8317b5777ae6abd23f5ff
Author: Chris Harrelson <chrishtr@chromium.org>
Date: Sat Mar 31 01:36:20 2018

[CI] Increase slop factor in DCHECK.

Bug:825742

Change-Id: I99a81da0a4275fcc6d5cb366f14706deaf3e686e
Reviewed-on: https://chromium-review.googlesource.com/987111
Reviewed-by: Stephen Chenney <schenney@chromium.org>
Commit-Queue: Chris Harrelson <chrishtr@chromium.org>
Cr-Commit-Position: refs/heads/master@{#547353}
[modify] https://crrev.com/91356a30f3c3df37ecd8317b5777ae6abd23f5ff/third_party/WebKit/Source/core/layout/LayoutGeometryMap.cpp

Status: Fixed (was: Assigned)
Project Member

Comment 6 by ClusterFuzz, Mar 31 2018

ClusterFuzz has detected this issue as fixed in range 547350:547353.

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

Fuzzer: marty_html_twiddler
Job Type: linux_debug_chrome
Platform Id: linux

Crash Type: CHECK failure
Crash Address: 
Crash State:
  layout_object_mapped_result.EqualWithinEpsilon(result.BoundingBox(), 0.1f) || la
  blink::LayoutGeometryMap::MapToAncestor
  blink::LayoutGeometryMap::AbsoluteRect
  
Sanitizer: address (ASAN)

Regressed: https://clusterfuzz.com/revisions?job=linux_debug_chrome&range=529050:529051
Fixed: https://clusterfuzz.com/revisions?job=linux_debug_chrome&range=547350:547353

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

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, Mar 31 2018

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