New issue
Advanced search Search tips

Issue 917754 link

Starred by 2 users
Status: WontFix
Owner:
pdr@chromium.org
Closed: Jan 3
Cc:
pnangunoori@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux
Pri: 1
Type: Bug



Sign in to add a comment

Null-dereference READ in blink::LocalFrameView::UpdateAllLifecyclePhases

Project Member Reported by ClusterFuzz, Dec 25 
Detailed report: https://clusterfuzz.com/testcase?key=5987278534737920

Fuzzer: inferno_twister
Job Type: linux_msan_content_shell_drt
Platform Id: linux

Crash Type: Null-dereference READ
Crash Address: 0x000000000030
Crash State:
  blink::LocalFrameView::UpdateAllLifecyclePhases
  blink::Internals::scrollsWithRespectTo
  blink::V8Internals::ScrollsWithRespectToMethodCallback
  
Sanitizer: memory (MSAN)

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

Issue filed automatically.

See https://www.chromium.org/developers/testing/memorysanitizer#TOC-Reproducing-ClusterFuzz-Bugs for instructions to reproduce this bug locally.

Comment 1 by pnangunoori@chromium.org, Dec 26

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

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

Comment 2 by vmp...@chromium.org, Jan 2

Components: Blink>Scroll
Owner: pdr@chromium.org
pdr, could you take a look?

Comment 3 by pdr@chromium.org, Jan 3

Status: WontFix (was: Assigned)
Internals::scrollsWithRespectTo is not checking that the nodes are in an active document like other DOM apis do (e.g., HTMLImageElement::width()). Because this is an internals-only function, I don't think we need to worry about this crash.
Project Member

Comment 4 by ClusterFuzz, Jan 10

Labels: Needs-Feedback
ClusterFuzz testcase 5987278534737920 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