CHECK failure: received_packet->ssrc == recovered_packet->ssrc in forward_error_correction.cc |
|||
Issue descriptionDetailed report: https://clusterfuzz.com/testcase?key=5417141942878208 Fuzzer: libFuzzer_flexfec_receiver_fuzzer Job Type: libfuzzer_chrome_asan_debug Platform Id: linux Crash Type: CHECK failure Crash Address: Crash State: received_packet->ssrc == recovered_packet->ssrc in forward_error_correction.cc rtc::FatalMessage::~FatalMessage webrtc::ForwardErrorCorrection::InsertMediaPacket Sanitizer: address (ASAN) Regressed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_asan_debug&range=476634:476682 Reproducer Testcase: https://clusterfuzz.com/download?testcase_id=5417141942878208 Issue filed automatically. See https://chromium.googlesource.com/chromium/src/+/master/testing/libfuzzer/reproducing.md for more information.
,
Jun 9 2017
ClusterFuzz has detected this issue as fixed in range 477952:477980. Detailed report: https://clusterfuzz.com/testcase?key=5417141942878208 Fuzzer: libFuzzer_flexfec_receiver_fuzzer Job Type: libfuzzer_chrome_asan_debug Platform Id: linux Crash Type: CHECK failure Crash Address: Crash State: received_packet->ssrc == recovered_packet->ssrc in forward_error_correction.cc rtc::FatalMessage::~FatalMessage webrtc::ForwardErrorCorrection::InsertMediaPacket Sanitizer: address (ASAN) Regressed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_asan_debug&range=476634:476682 Fixed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_asan_debug&range=477952:477980 Reproducer Testcase: https://clusterfuzz.com/download?testcase_id=5417141942878208 See https://chromium.googlesource.com/chromium/src/+/master/testing/libfuzzer/reproducing.md for more information. If you suspect that the result above is incorrect, try re-doing that job on the test case report page.
,
Jun 9 2017
,
Jun 12 2017
brandtr@ could you add the CL that fixed it in this bug? Also, did you add a test to cover for this?
,
Jun 12 2017
This was fixed by reverting the change that introduced the problem. https://codereview.webrtc.org/2919313005/ The CL has not been relanded yet; trying to figure out how to deal with the problem is a nice way. |
|||
►
Sign in to add a comment |
|||
Comment 1 by msrchandra@chromium.org
, Jun 5 2017Components: Blink>WebRTC
Labels: M-60 Test-Predator-Correct-CLs
Owner: brandtr@chromium.org
Status: Assigned (was: Untriaged)