CHECK failure: g_iat_orig_duplicate_handle(target_process_handle, *target_handle, ::GetCurrentP |
|||||||
Issue descriptionDetailed report: https://clusterfuzz.com/testcase?key=5713118780194816 Fuzzer: inferno_layout_test_unmodified Job Type: windows_asan_content_shell Platform Id: windows Crash Type: CHECK failure Crash Address: Crash State: g_iat_orig_duplicate_handle(target_process_handle, *target_handle, ::GetCurrentP service_manager::DuplicateHandlePatch mojo::edk::Channel::Message::RewriteHandles Sanitizer: address (ASAN) Reproducer Testcase: https://clusterfuzz.com/download?testcase_id=5713118780194816 Issue filed automatically. See https://github.com/google/clusterfuzz-tools for more information.
,
Nov 1 2017
Predator and CL could not provide any possible suspects. Using the code search for the file, “sandbox_win.cc” assigning to concern owner. Suspecting Commit# https://chromium.googlesource.com/chromium/src/+/f4f97a92633d239cfd7911dc576600ff8c0dd4b0 tsepez@ -- Could you please look into this issue, kindly reassign if it has nothing to do with your changes. Thank You.
,
Nov 2 2017
Will, could you try to reproduce this? Another consequence of moving the duplicate handle check into a different dll, I would imagine.
,
Nov 2 2017
,
Jun 19 2018
ClusterFuzz testcase 5713118780194816 appears to be flaky, updating reproducibility label.
,
Jun 19 2018
ClusterFuzz testcase 5713118780194816 is flaky and no longer crashes, so closing issue. If this is incorrect, please add ClusterFuzz-Wrong label and re-open the issue.
,
Jun 19 2018
Automatically applying components based on crash stacktrace and information from OWNERS files. If this is incorrect, please apply the Test-Predator-Wrong-Components label. |
|||||||
►
Sign in to add a comment |
|||||||
Comment 1 by dtapu...@chromium.org
, Oct 31 2017