New issue
Advanced search Search tips

Issue 820611 link

Starred by 2 users

Issue metadata

Status: Duplicate
Merged: issue 808390
Owner: ----
Closed: Mar 2018
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux
Pri: 1
Type: Bug



Sign in to add a comment

Indirect-leak in content::RenderFrameImpl::WillSendRequest

Project Member Reported by ClusterFuzz, Mar 9 2018

Issue description

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

Fuzzer: attekett_surku_fuzzer
Job Type: linux_lsan_chrome_mp
Platform Id: linux

Crash Type: Indirect-leak
Crash Address: 
Crash State:
  content::RenderFrameImpl::WillSendRequest
  blink::LocalFrameClientImpl::DispatchWillSendRequest
  blink::FrameFetchContext::PrepareRequest
  
Sanitizer: address (ASAN)

Regressed: https://clusterfuzz.com/revisions?job=linux_lsan_chrome_mp&range=523898:523900

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

Additional requirements: Requires Gestures

Issue filed automatically.

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

Comment 1 by ClusterFuzz, Mar 9 2018

Components: Blink 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.

Comment 2 by kochi@chromium.org, Mar 10 2018

Components: -Blink -Internals>Core Blink>Network
As the original caller is from resource fetcher in Blink,
could someone in blink network further triage this?
Mergedinto: 808390
Status: Duplicate (was: Untriaged)
 
 Issue 822610  has been merged into this issue.
 Issue 824737  has been merged into this issue.

Sign in to add a comment