New issue
Advanced search Search tips

Issue 822610 link

Starred by 1 user
Status: Duplicate
Merged: issue 820611
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 16 2018 
Detailed report: https://clusterfuzz.com/testcase?key=6325155639590912

Fuzzer: inferno_layout_test_unmodified
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=6325155639590912

Issue filed automatically.

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

Comment 1 by ClusterFuzz, Mar 16 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.
Project Member

Comment 2 by ClusterFuzz, Mar 16 2018

Labels: Test-Predator-Auto-Owner
Owner: timbrown@chromium.org
Status: Assigned (was: Untriaged)
Automatically assigning owner based on suspected regression changelist https://chromium.googlesource.com/chromium/src/+/c1829894ac62e37257973d5e5c27d1bffb9888b3 (Remove remaining references to gconf).

If this is incorrect, please let us know why and apply the Test-Predator-Wrong-CLs label. If you aren't the correct owner for this issue, please unassign yourself as soon as possible so it can be re-triaged.

Comment 3 by timbrown@chromium.org, Mar 16 2018

Labels: Test-Predator-Wrong-CLs
Owner: ----
Status: Untriaged (was: Assigned)
My CL (the one linked) is a no-op. It is comment changes and the removal of dead code. I don't see how it could affect the blink code at all.

Comment 4 by brajkumar@chromium.org, Mar 20 2018

Mergedinto: 820611
Status: Duplicate (was: Untriaged)
This issue looks similar to  bug 820611 , hence merging in to it . Feel free to undupe if it's a different issue.

Thanks!
►

Sign in to add a comment