Indirect-leak in IPC::ChannelProxy::Context::Context |
|||||
Issue descriptionDetailed report: https://clusterfuzz.com/testcase?key=6480365506789376 Fuzzer: inferno_twister_c Job Type: linux_lsan_chrome_mp Platform Id: linux Crash Type: Indirect-leak Crash Address: Crash State: IPC::ChannelProxy::Context::Context SyncContext IPC::SyncChannel::SyncChannel Sanitizer: address (ASAN) Regressed: https://clusterfuzz.com/revisions?job=linux_lsan_chrome_mp&range=453344:453369 Reproducer Testcase: https://clusterfuzz.com/download?testcase_id=6480365506789376 Issue filed automatically. See https://github.com/google/clusterfuzz-tools for more information.
,
Feb 5 2018
Predator and CL could not provide any possible suspects. Using the code search for the file, “ipc_sync_channel.cc” assigning to concern owner from GIT blame. Suspecting Commit# https://chromium.googlesource.com/chromium/src/+/ff15e975de135dd54b1572e5b9a53f47e8a0df7a @hajimehoshi -- Could you please look into this issue, kindly reassign if it has nothing to do with your changes. Thank You.
,
Feb 6 2018
,
Feb 6 2018
I don't think the CL changed the behavior? Anyway I'll take a look...
,
Feb 6 2018
The cluster fuzz says https://chromium.googlesource.com/chromium/src/+/9a421fa170335630f5c714e5a12049664095f964/ipc/ipc_channel_proxy.cc#39 is leaked, but this is a unique_ptr. Hmm?
,
Jul 12
ClusterFuzz testcase 6480365506789376 appears to be flaky, updating reproducibility label.
,
Jul 12
ClusterFuzz testcase 6480365506789376 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 |
|||||
Comment 1 by ClusterFuzz
, Feb 4 2018Labels: Test-Predator-Auto-Components