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

Issue 810976 link

Starred by 2 users

Issue metadata

Status: WontFix
Owner: ----
Closed: Jun 2018
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux
Pri: 1
Type: Bug

Blocked on:
issue 771272



Sign in to add a comment

Indirect-leak in content::WebURLLoaderImpl::PopulateURLResponse

Project Member Reported by ClusterFuzz, Feb 10 2018

Issue description

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

Fuzzer: inferno_layout_test_unmodified
Job Type: linux_lsan_chrome_mp
Platform Id: linux

Crash Type: Indirect-leak
Crash Address: 
Crash State:
  content::WebURLLoaderImpl::PopulateURLResponse
  content::WebURLLoaderImpl::Context::OnReceivedResponse
  content::ResourceDispatcher::OnReceivedResponse
  
Sanitizer: address (ASAN)

Regressed: https://clusterfuzz.com/revisions?job=linux_lsan_chrome_mp&range=461632:461638

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

Issue filed automatically.

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

Comment 1 by ClusterFuzz, Feb 10 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.
Cc: brajkumar@chromium.org
Labels: Test-Predator-Wrong
Owner: rdsmith@chromium.org
Status: Assigned (was: Untriaged)
Predator and CL could not provide any possible suspects.

Using Code Search for the file, "web_url_loader_impl.cc" and observed there was some recent changes for the below file.

Suspect CL: https://chromium.googlesource.com/chromium/src/+/ff094aa1ff9e127c69dd2ccac13e18fd02730ab4%5E%21/content/renderer/loader/web_url_loader_impl.cc

rdsmith@ -- 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!
My change wasn't even plumbing; it was moving an include file between directories and changing all references to the types in it.  So I don't think of any way it could have caused a leak.

Would you help me understand why this problem can't be easily bisected?  Is the failure flaky?

Blockedon: 771272
This seems to be flaky. Now the CF report (https://clusterfuzz.com/v2/testcase-detail/6414717569204224?noredirect=1) is saying "Reproducible: No".
Owner: ----
Status: Untriaged (was: Assigned)
I'm afraid I'm just going to abandon this issue.  I don't think it's something I've done, and I'm leaving the project at the end of the month, so it's unlikely to me that I'll find time to look at it before then.
Labels: CF-NeedsTriage
Project Member

Comment 7 by ClusterFuzz, Jun 26 2018

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