Direct-leak in ebml_parse_elem |
|||||
Issue descriptionDetailed report: https://cluster-fuzz.appspot.com/testcase?key=5858543067987968 Fuzzer: media_pipeline_integration_fuzzer Job Type: libfuzzer_chrome_asan Platform Id: linux Crash Type: Direct-leak Crash Address: Crash State: ebml_parse_elem ebml_parse_id ebml_parse Unminimized Testcase: https://cluster-fuzz.appspot.com/download/AMIfv953prj6IFvp8Wlfp6jqekUY5IDFJU1wulWGcVIYMafE3fL1yEcqAx2U89k_udsF-nB-2curstStTHAMn34YWUIxOE18P_aUVAkb36Y5xeh8Vt2OKOpRQq6b7W3-tGZyBStftV7eR_iGESHjc_bWBhUWp516bw Filer: mmoroz See https://dev.chromium.org/Home/chromium-security/bugs/reproducing-clusterfuzz-bugs for more information.
,
May 3 2016
,
May 3 2016
,
Jul 28 2016
Detailed report: https://cluster-fuzz.appspot.com/testcase?key=6453516218662912 Fuzzer: attekett_surku_fuzzer Job Type: linux_lsan_chrome_mp Platform Id: linux Crash Type: Direct-leak Crash Address: Crash State: ebml_parse_elem ebml_parse ebml_parse_elem Regressed: https://cluster-fuzz.appspot.com/revisions?job=linux_lsan_chrome_mp&range=262146:262202 Minimized Testcase (4.41 Kb): https://cluster-fuzz.appspot.com/download/AMIfv965nO6tgXOHRrFyr2rs4eqMi3a5a6CLvCaLU7PA2zkgVmwCdygB8jFLJwxcEE_KEKDPmwLlG9e22xY5qeARfCw55C304vKWKNqXcQFKAGw1h6WmZ5s9dIYdzn45aFZ90jeTAI7bg52cdZ-hMm7e1W1wYVguJw?testcase_id=6453516218662912 Filer: rnimmagadda See https://dev.chromium.org/Home/chromium-security/bugs/reproducing-clusterfuzz-bugs for more information.
,
Sep 11 2016
ClusterFuzz has detected this issue as fixed in range 415049:415600. Detailed report: https://cluster-fuzz.appspot.com/testcase?key=6453516218662912 Fuzzer: attekett_surku_fuzzer Job Type: linux_lsan_chrome_mp Platform Id: linux Crash Type: Direct-leak Crash Address: Crash State: ebml_parse_elem ebml_parse ebml_parse_elem Regressed: https://cluster-fuzz.appspot.com/revisions?job=linux_lsan_chrome_mp&range=262146:262202 Fixed: https://cluster-fuzz.appspot.com/revisions?job=linux_lsan_chrome_mp&range=415049:415600 Minimized Testcase (4.41 Kb): https://cluster-fuzz.appspot.com/download/AMIfv965nO6tgXOHRrFyr2rs4eqMi3a5a6CLvCaLU7PA2zkgVmwCdygB8jFLJwxcEE_KEKDPmwLlG9e22xY5qeARfCw55C304vKWKNqXcQFKAGw1h6WmZ5s9dIYdzn45aFZ90jeTAI7bg52cdZ-hMm7e1W1wYVguJw?testcase_id=6453516218662912 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.
,
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
,
Dec 2 2016
jrummell@ Did the roll (M56 issue 591845 ) fix this? Regardless, the fix might be needed in M55 (and upstream ffmpeg, and a test added to ffmpeg_regression_tests).
,
Dec 12 2016
This is no longer reproducible. Marking this as fixed by the ffmpeg roll. [2016-12-12 20:13:28 UTC] Redo task(s): blame, impact, minimize, progression, regression [2016-12-12 20:14:07 UTC] Minimize task started. [2016-12-12 20:30:48 UTC] Minimize task errored out: Unable to reproduce crash. [2016-12-12 20:32:02 UTC] Minimize task started. [2016-12-12 20:38:32 UTC] Minimize task errored out: Unable to reproduce crash. [2016-12-12 20:38:32 UTC] Minimize task errored out: Test case appears to be flaky. |
|||||
►
Sign in to add a comment |
|||||
Comment 1 by mmoroz@chromium.org
, Apr 15 2016Owner: jrumm...@chromium.org