iter != handle_map_.end() in speech_recognition_dispatcher.cc |
||||||
Issue descriptionDetailed report: https://cluster-fuzz.appspot.com/testcase?key=4896581497389056 Fuzzer: inferno_twister Job Type: linux_tsan_chrome_mp Platform Id: linux Crash Type: CHECK failure Crash Address: Crash State: iter != handle_map_.end() in speech_recognition_dispatcher.cc backtrace content::SpeechRecognitionDispatcher::OnErrorOccurred Regressed: https://cluster-fuzz.appspot.com/revisions?job=linux_tsan_chrome_mp&range=402485:402738 Minimized Testcase (0.21 Kb): Download: https://cluster-fuzz.appspot.com/download/AMIfv95Jztrln0-Pfh3lI6MADpPshn7TH8y_5vL8DT-tgLd-cACgXcJpUMc09KMgVng8gJK-Cr0GZRVv58emPQtYCV6_lFHsfH3aZlCn3rJvF9dnpsG_vTZmnwm3ThV6lpK9YU7uchT42gKGfIREiXtWqCsmDZJ8wQ?testcase_id=4896581497389056 <html><head><script> var recognition = new webkitSpeechRecognition(); recognition.onend = function() { recognition.start(); recognition.stop(); }; recognition.start(); </script></head><body id=tCF1>,z Filer: mummareddy See https://dev.chromium.org/Home/chromium-security/bugs/reproducing-clusterfuzz-bugs for more information.
,
Jul 19 2016
,
Jul 19 2016
,
Jul 22 2016
Looping in chromium//src/content/renderer/OWNERS as per the only file speech_recognition_dispatcher.cc shown in the stack trace. esprehn@, can you please take a look at this issue ?
,
Jul 23 2016
ClusterFuzz has detected this issue as fixed in range 407167:407197. Detailed report: https://cluster-fuzz.appspot.com/testcase?key=4896581497389056 Fuzzer: inferno_twister Job Type: linux_tsan_chrome_mp Platform Id: linux Crash Type: CHECK failure Crash Address: Crash State: iter != handle_map_.end() in speech_recognition_dispatcher.cc backtrace content::SpeechRecognitionDispatcher::OnErrorOccurred Regressed: https://cluster-fuzz.appspot.com/revisions?job=linux_tsan_chrome_mp&range=402485:402738 Fixed: https://cluster-fuzz.appspot.com/revisions?job=linux_tsan_chrome_mp&range=407167:407197 Minimized Testcase (0.21 Kb): Download: https://cluster-fuzz.appspot.com/download/AMIfv95Jztrln0-Pfh3lI6MADpPshn7TH8y_5vL8DT-tgLd-cACgXcJpUMc09KMgVng8gJK-Cr0GZRVv58emPQtYCV6_lFHsfH3aZlCn3rJvF9dnpsG_vTZmnwm3ThV6lpK9YU7uchT42gKGfIREiXtWqCsmDZJ8wQ?testcase_id=4896581497389056 <html><head><script> var recognition = new webkitSpeechRecognition(); recognition.onend = function() { recognition.start(); recognition.stop(); }; recognition.start(); </script></head><body id=tCF1>,z 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.
,
Jul 23 2016
ClusterFuzz testcase is verified as fixed, closing issue. If this is incorrect, please add ClusterFuzz-Wrong label and re-open the issue.
,
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 |
||||||
►
Sign in to add a comment |
||||||
Comment 1 by mummare...@chromium.org
, Jul 18 2016