Indirect-leak in IPC::ChannelProxy::Context::Context |
|||
Issue descriptionDetailed 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.
,
May 16 2017
The change in question was a mechanical change that should not have affected behavior. Assigning to dcheng@, could you triage/reassign please?
,
Jun 15 2017
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 |
|||
Comment 1 by msrchandra@chromium.org
, May 16 2017Components: Internals>Core
Labels: Test-Predator-Correct-CLs
Owner: vmp...@chromium.org
Status: Assigned (was: Untriaged)