CHECK failure: false in scoped_handle_verifier.cc |
||||
Issue descriptionDetailed report: https://clusterfuzz.com/testcase?key=5711581129998336 Fuzzer: libFuzzer_mojo_core_node_channel_fuzzer Fuzz target binary: mojo_core_node_channel_fuzzer Job Type: windows_libfuzzer_chrome_asan Platform Id: windows Crash Type: CHECK failure Crash Address: Crash State: false in scoped_handle_verifier.cc base::win::internal::ScopedHandleVerifier::StartTracking base::win::VerifierTraits::StartTracking Sanitizer: address (ASAN) Regressed: https://clusterfuzz.com/revisions?job=windows_libfuzzer_chrome_asan&range=611580:611589 Reproducer Testcase: https://clusterfuzz.com/download?testcase_id=5711581129998336 Issue filed automatically. See https://chromium.googlesource.com/chromium/src/+/master/testing/libfuzzer/reproducing.md for instructions to reproduce this bug locally.
,
Jan 20
(2 days ago)
Automatically applying components based on crash stacktrace and information from OWNERS files. If this is incorrect, please apply the Test-Predator-Wrong-Components label.
,
Jan 20
(2 days ago)
Automatically assigning owner based on suspected regression changelist https://chromium.googlesource.com/chromium/src/+/24170150bbeeecdae6edc86ae98ad9c9fca77aa8 ([mojo-core] Add fuzzers for Channel & NodeChannel). 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.
,
Yesterday
(40 hours ago)
Please take a look as this is marked as RB-Beta for M-73. |
||||
►
Sign in to add a comment |
||||
Comment 1 by ClusterFuzz
, Jan 20 (2 days ago)