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

Issue 810660 link

Starred by 1 user
Status: WontFix
Owner: ----
Closed: Feb 2018
Cc:
█ roc...@chromium.org
hirosh...@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux
Pri: 1
Type: Bug



Sign in to add a comment

Indirect-leak in content::SiteIsolationStatsGatherer::OnReceivedResponse

Project Member Reported by ClusterFuzz, Feb 9 2018 
Detailed report: https://clusterfuzz.com/testcase?key=5437879602642944

Fuzzer: inferno_twister
Job Type: linux_lsan_chrome_mp
Platform Id: linux

Crash Type: Indirect-leak
Crash Address: 
Crash State:
  content::SiteIsolationStatsGatherer::OnReceivedResponse
  content::ResourceDispatcher::OnReceivedResponse
  content::URLLoaderClientImpl::OnReceiveResponse
  
Sanitizer: address (ASAN)

Regressed: https://clusterfuzz.com/revisions?job=linux_lsan_chrome_mp&range=491480:491565

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

Additional requirements: Requires HTTP

Issue filed automatically.

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

Comment 1 by ClusterFuzz, Feb 9 2018

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, Feb 9 2018

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

Remove unnecessary SetUpContext usage by rockot@chromium.org - https://chromium.googlesource.com/chromium/src/+/dd536442dfab83c16649ec1709a28801f5d0656c

Move SubresourceIntegrity calls to Resource by hiroshige@chromium.org - https://chromium.googlesource.com/chromium/src/+/3305344cb14705b1c8cb802cfd65e49d375aff85

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

Comment 3 by roc...@chromium.org, Feb 12 2018 

I don't think my change is relevant. The SubresourceIntegrity change is more plausible given that it looks like it's at least changing behavior of renderer-side resource loading code, but nothing specific about the CL stands out to me.

I think this has just been (racy and) leaky. Looks like the leak is a SiteIsolationResponseMetaData, which is owned exclusively by a ResourceDispatcher::PendingRequestInfo. PendingRequestInfo in turn is always deleted asynchronously.

Presumably this leak is seen when the posted deletion task doesn't get to run before shutdown.
Project Member

Comment 4 by ClusterFuzz, Feb 23 2018

Status: WontFix (was: Untriaged)
ClusterFuzz testcase 5437879602642944 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