New issue
Advanced search Search tips

Issue 868961 link

Starred by 1 user
Status: WontFix
Owner:
chrishtr@chromium.org
Closed: Jul 31
Cc:
pnangunoori@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux
Pri: 1
Type: Bug



Sign in to add a comment

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

Project Member Reported by ClusterFuzz, Jul 30 
Detailed report: https://clusterfuzz.com/testcase?key=5639328882229248

Fuzzer: bj_broddelwerk
Job Type: linux_debug_chrome
Platform Id: linux

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

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

Issue filed automatically.

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

Comment 1 by pnangunoori@chromium.org, Jul 31

Cc: pnangunoori@chromium.org
Components: Blink>WebAudio
Labels: M-68 Test-Predator-Wrong
Owner: chrishtr@chromium.org
Status: Assigned (was: Untriaged)
Predator and CL could not provide any possible suspects.
Using the code search for the file, “layout_geometry_map.cc” assigning to owner concerned from GIT blame.
Suspecting Commit#
https://chromium.googlesource.com/chromium/src/+/ade7041fc934d855bcbdc3a4d5bd9adb199def7c

@chrishtr-- Could you please look into this issue, kindly reassign if it has nothing to do with your changes.
Thank You.

Comment 2 by chrishtr@chromium.org, Jul 31

Status: WontFix (was: Assigned)
This DCHECK is not relevant to security, only correctness. And the testcase
uses extreme layout values to trigger floating point error.

Comment 3 by rtoy@chromium.org, Jul 31

Components: -Blink>WebAudio Blink>Layout
This is not a WebAudio issue either.  Setting component to Layout, for the record.
Project Member

Comment 4 by ClusterFuzz, Aug 7

Labels: Needs-Feedback
ClusterFuzz testcase 5639328882229248 is still reproducing on tip-of-tree build (trunk).

If this testcase was not reproducible locally or unworkable, ignore this notification and we will file another bug soon with hopefully a better and workable testcase.

Otherwise, if this is not intended to be fixed (e.g. this is an intentional crash), please add ClusterFuzz-Ignore label to prevent future bug filing with similar crash stacktrace.
►

Sign in to add a comment