success in vie_encoder.cc |
||||||
Issue descriptionDetailed report: https://cluster-fuzz.appspot.com/testcase?key=5032748253446144 Fuzzer: inferno_layout_test_unmodified Job Type: linux_debug_content_shell_drt Platform Id: linux Crash Type: CHECK failure Crash Address: Crash State: success in vie_encoder.cc rtc::FatalMessage::~FatalMessage webrtc::ViEEncoder::ReconfigureEncoder webrtc::ViEEncoder::EncodeVideoFrame Regressed: https://cluster-fuzz.appspot.com/revisions?job=linux_debug_content_shell_drt&range=382043:382135 Minimized Testcase (7.31 Kb): https://cluster-fuzz.appspot.com/download/AMIfv941-u017WK5FExZQxramDRW-yRoCz9Ob-Zd8J31f-9mFeVfD1hqOLaur2IZYusUhL5RBY5uvpuMBKuSvmDdLMqVfkKxw4w3zMdNEmtKORtJfobgKM1S_002QBzOa-mheOKvlfaqIRLvOqwZN6i0IqL-JqDkWw?testcase_id=5032748253446144 Issue filed automatically. See https://dev.chromium.org/Home/chromium-security/bugs/reproducing-clusterfuzz-bugs for more information.
,
Oct 28 2016
I don't know this code. I guess you may want to find someone from webrtc team to take a look.
,
Oct 28 2016
,
Nov 22 2016
Removing EditIssue view restrictions from ClusterFuzz filed bugs. If you believe that this issue should still be restricted, please reapply the label. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Jan 24 2017
,
Mar 31 2017
ClusterFuzz has detected this issue as fixed in range 460757:460789. Detailed report: https://clusterfuzz.com/testcase?key=5032748253446144 Fuzzer: inferno_layout_test_unmodified Job Type: linux_debug_content_shell_drt Platform Id: linux Crash Type: CHECK failure Crash Address: Crash State: success in vie_encoder.cc rtc::FatalMessage::~FatalMessage webrtc::ViEEncoder::ReconfigureEncoder Sanitizer: address (ASAN) Regressed: https://clusterfuzz.com/revisions?job=linux_debug_content_shell_drt&range=382043:382135 Fixed: https://clusterfuzz.com/revisions?job=linux_debug_content_shell_drt&range=460757:460789 Reproducer Testcase: https://clusterfuzz.com/download/AMIfv96EOfEAdJjOzyr-7urBdwoKCP-QcRh5ORzphP5UTlKwd4BZxes_BC3l6K5736ZPs6BjVlSrtgGET0-MklKg3JeWwoACkv8pjS1WcAFEoTS8RRoFmo4kn9-xwn4YJnt54PebUZiZoqoX5iOplaE8yJSmbQ6tc17W3E9HGKdeNX_e2v3Wx2xDUbV26t0IkZNTHOydVojQu_IebAQMBcpxSiksynUEXiB-8TZSv7OazdhAWaw0S2rnA4Wmn9gUwxWSP4OdqrMG0HSqoHtwwSSigGI1-lErkiGnBxp-cBl-pfoNWZJZ0HLLFVApxFHdQIjenQz_nmIx46f6CVX5u6cq6xggdZnLFagPTK0JSBDER38RE9mXG-_jd2auzNzhVaWpL5mwZomrT9t2IufxqBTn7dp3BcAzSA?testcase_id=5032748253446144 See https://dev.chromium.org/Home/chromium-security/bugs/reproducing-clusterfuzz-bugs for more information. If you suspect that the result above is incorrect, try re-doing that job on the test case report page.
,
Mar 31 2017
ClusterFuzz testcase 5032748253446144 is verified as fixed, so closing issue. If this is incorrect, please add ClusterFuzz-Wrong label and re-open the issue. |
||||||
►
Sign in to add a comment |
||||||
Comment 1 by mmohammad@chromium.org
, Oct 27 2016Status: Assigned (was: Untriaged)