CHECK failure: n != 4 in source_buffer_state.cc |
||||
Issue descriptionDetailed report: https://clusterfuzz.com/testcase?key=4865451552407552 Fuzzer: libFuzzer_mediasource_MP2T_AVC_pipeline_integration_fuzzer Job Type: libfuzzer_chrome_asan_debug Platform Id: linux Crash Type: CHECK failure Crash Address: Crash State: n != 4 in source_buffer_state.cc media::SourceBufferState::Append media::ChunkDemuxer::AppendData Sanitizer: address (ASAN) Regressed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_asan_debug&range=512405:512408 Reproducer Testcase: https://clusterfuzz.com/download?testcase_id=4865451552407552 Issue filed automatically. See https://chromium.googlesource.com/chromium/src/+/master/testing/libfuzzer/reference.md for more information.
,
Oct 29 2017
,
Oct 30 2017
Testcase 4865451552407552 is a top crash on ClusterFuzz for linux platform. Please prioritize fixing this crash. Marking this crash as a Beta release blocker. If this is incorrect, please add ClusterFuzz-Wrong label and re-open the issue.
,
Oct 30 2017
This issue is similar to the Issue 779379 , hence merging into it. Please undo it if anybody feel so Thank You...
,
Nov 1 2017
ClusterFuzz has detected this issue as fixed in range 512880:512907. Detailed report: https://clusterfuzz.com/testcase?key=4865451552407552 Fuzzer: libFuzzer_mediasource_MP2T_AVC_pipeline_integration_fuzzer Job Type: libfuzzer_chrome_asan_debug Platform Id: linux Crash Type: CHECK failure Crash Address: Crash State: n != 4 in source_buffer_state.cc media::SourceBufferState::Append media::ChunkDemuxer::AppendData Sanitizer: address (ASAN) Regressed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_asan_debug&range=512405:512408 Fixed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_asan_debug&range=512880:512907 Reproducer Testcase: https://clusterfuzz.com/download?testcase_id=4865451552407552 See https://chromium.googlesource.com/chromium/src/+/master/testing/libfuzzer/reference.md for more information. If you suspect that the result above is incorrect, try re-doing that job on the test case report page. |
||||
►
Sign in to add a comment |
||||
Comment 1 by ClusterFuzz
, Oct 29 2017