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

Issue 722689 link

Starred by 1 user

Issue metadata

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



Sign in to add a comment

Indirect-leak in IPC::ChannelProxy::Context::Context

Project Member Reported by ClusterFuzz, May 16 2017

Issue description

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

Fuzzer: ochang_domfuzzer
Job Type: linux_asan_content_shell_drt
Platform Id: linux

Crash Type: Indirect-leak
Crash Address: 
Crash State:
  IPC::ChannelProxy::Context::Context
  IPC::SyncChannel::SyncContext::SyncContext
  IPC::SyncChannel::SyncChannel
  
Sanitizer: address (ASAN)

Regressed: https://clusterfuzz.com/revisions?job=linux_asan_content_shell_drt&range=406944:407004

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


Issue filed automatically.

See https://dev.chromium.org/Home/chromium-security/bugs/reproducing-clusterfuzz-bugs for more information.
 
Cc: msrchandra@chromium.org
Components: Internals>Core
Labels: Test-Predator-Correct-CLs
Owner: vmp...@chromium.org
Status: Assigned (was: Untriaged)
Assigning to concern owner from Predator results --
The result is a list of CLs that change the crashed files. 

Author: vmpstr
Project: chromium
Changelist: https://chromium.googlesource.com/chromium/src/+/10e0d5f672745230042c700577feb7fc66f00f15
Time: Thu Jul 21 23:46:09 2016
File child_thread_impl.cc is changed in this cl (and is part of stack frame #5, "content::ChildThreadImpl::Init")
Minimum distance from crash line to modified line: 67. (file: child_thread_impl.cc, crashed on: 440, modified: 507).

@vmpstr -- Could you please look into the issue, kindly re-assign if this is not related to your changes.
Thank You.

Comment 2 by vmp...@chromium.org, May 16 2017

Cc: vmp...@chromium.org
Owner: dcheng@chromium.org
The change in question was a mechanical change that should not have affected behavior. Assigning to dcheng@, could you triage/reassign please?
Project Member

Comment 3 by ClusterFuzz, Jun 15 2017

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

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

Sign in to add a comment