New issue
Advanced search Search tips
Note: Color blocks (like █ or █) mean that a user may not be available. Tooltip shows the reason.

Issue 904141 link

Starred by 1 user
Status: WontFix
Owner:
paulmeyer@chromium.org
Closed: Dec 7
Cc:
lfg@chromium.org
█ ben@chromium.org
kkaluri@chromium.org
ekaramad@chromium.org
mthiesse@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux
Pri: 1
Type: Bug



Sign in to add a comment

Null-dereference READ in content::WebContentsImpl::GetInnerWebContents

Project Member Reported by ClusterFuzz, Nov 10 
Detailed report: https://clusterfuzz.com/testcase?key=6194114946924544

Fuzzer: ipc_fuzzer_mut
Job Type: linux_asan_chrome_ipc
Platform Id: linux

Crash Type: Null-dereference READ
Crash Address: 0x000000000000
Crash State:
  content::WebContentsImpl::GetInnerWebContents
  content::WebContentsImpl::GetWebContentsAndAllInner
  content::WebContentsImpl::GetOrCreateFindRequestManager
  
Sanitizer: address (ASAN)

Regressed: https://clusterfuzz.com/revisions?job=linux_asan_chrome_ipc&range=488146:488576

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

Additional requirements: Requires Gestures

Issue filed automatically.

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

Comment 1 by ClusterFuzz, Nov 10

Components: Internals>Core
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, Nov 10

Cc: mthiesse@chromium.org ben@chromium.org
Labels: Test-Predator-Auto-CC
Automatically adding ccs based on suspected regression changelists:

Allow WebContentsObservers to bind InterfaceRequests from frames. by ben@chromium.org - https://chromium.googlesource.com/chromium/src/+/9e24929e2983a0bd95da806f307cfdffc5367688

VR: Check focus state browser-side before sending input to renderer. by mthiesse@chromium.org - https://chromium.googlesource.com/chromium/src/+/896405dba79929bde34c1473583fc4facc6436a9

If this is incorrect, please let us know why and apply the Test-Predator-Wrong-CLs label.

Comment 3 by mthiesse@chromium.org, Nov 12 

Given the stack it's almost certainly not my CL.

Comment 4 by kkaluri@chromium.org, Nov 13

Cc: kkaluri@chromium.org
Labels: M-72
Owner: lfg@chromium.org
Status: Assigned (was: Untriaged)
Predator and CL could not provide any possible suspects.

Using Code Search for the file, "web_contents_impl.cc" suspecting the below Cl might have caused this issue

Suspect CL: https://chromium.googlesource.com/chromium/src/+/3d38ec15f7bac87f25a53172e4f21e0d950618ca

lfg@ -- Could you please check whether this is caused with respect to your change, if not please help us in assigning it to the right owner.

Thanks!

Comment 5 by lfg@chromium.org, Nov 15

Cc: ekaramad@chromium.org lfg@chromium.org
Owner: paulmeyer@chromium.org
Project Member

Comment 6 by ClusterFuzz, Nov 19

Labels: -Reproducible Unreproducible
ClusterFuzz testcase 6194114946924544 appears to be flaky, updating reproducibility label.
Project Member

Comment 7 by ClusterFuzz, Dec 7

Status: WontFix (was: Assigned)
ClusterFuzz testcase 6194114946924544 is flaky and no longer crashes, so closing issue.

If this is incorrect, please add ClusterFuzz-Wrong label and re-open the issue.
►

Sign in to add a comment