CHECK failure: !Allocator::IsObjectResurrectionForbidden() in vector.h |
|||
Issue descriptionDetailed report: https://clusterfuzz.com/testcase?key=6265332318339072 Fuzzer: inferno_twister_c Job Type: linux_asan_content_shell_drt Platform Id: linux Crash Type: CHECK failure Crash Address: Crash State: !Allocator::IsObjectResurrectionForbidden() in vector.h void WTF::Vector<blink::Member<blink::Event>, 0u, blink::HeapAllocator>::AppendS blink::MediaStream::ScheduleDispatchEvent Sanitizer: address (ASAN) Regressed: https://clusterfuzz.com/revisions?job=linux_asan_content_shell_drt&range=580853:580854 Reproducer Testcase: https://clusterfuzz.com/download?testcase_id=6265332318339072 Issue filed automatically. See https://github.com/google/clusterfuzz-tools for instructions to reproduce this bug locally.
,
Dec 27
Automatically assigning owner based on suspected regression changelist https://chromium.googlesource.com/chromium/src/+/5d50bd43c0312f7323d2d5652af22fedda3a4d8a (Retire MediaCaptureFromVideo runtime flag). 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.
,
Jan 3
ClusterFuzz has detected this issue as fixed in range 619628:619629. Detailed report: https://clusterfuzz.com/testcase?key=6265332318339072 Fuzzer: inferno_twister_c Job Type: linux_asan_content_shell_drt Platform Id: linux Crash Type: CHECK failure Crash Address: Crash State: !Allocator::IsObjectResurrectionForbidden() in vector.h void WTF::Vector<blink::Member<blink::Event>, 0u, blink::HeapAllocator>::AppendS blink::MediaStream::ScheduleDispatchEvent Sanitizer: address (ASAN) Regressed: https://clusterfuzz.com/revisions?job=linux_asan_content_shell_drt&range=580853:580854 Fixed: https://clusterfuzz.com/revisions?job=linux_asan_content_shell_drt&range=619628:619629 Reproducer Testcase: https://clusterfuzz.com/download?testcase_id=6265332318339072 See https://github.com/google/clusterfuzz-tools for instructions to reproduce this bug locally. If you suspect that the result above is incorrect, try re-doing that job on the test case report page.
,
Jan 3
ClusterFuzz testcase 6265332318339072 is verified as fixed, so closing issue as verified. If this is incorrect, please add ClusterFuzz-Wrong label and re-open the issue. |
|||
►
Sign in to add a comment |
|||
Comment 1 by ClusterFuzz
, Dec 27Labels: Test-Predator-Auto-Components