New issue
Advanced search Search tips

Issue 839171 link

Starred by 1 user

Issue metadata

Status: WontFix
Owner:
Closed: May 2018
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux
Pri: 1
Type: Bug



Sign in to add a comment

CHECK failure: iter != handle_map_.end() in speech_recognition_dispatcher.cc

Project Member Reported by ClusterFuzz, May 2 2018

Issue description

Detailed report: https://clusterfuzz.com/testcase?key=6506050946334720

Fuzzer: mojo_fuzzer
Job Type: linux_asan_chrome_mojo
Platform Id: linux

Crash Type: CHECK failure
Crash Address: 
Crash State:
  iter != handle_map_.end() in speech_recognition_dispatcher.cc
  content::SpeechRecognitionDispatcher::OnErrorOccurred
  bool IPC::MessageT<SpeechRecognitionMsg_ErrorOccurred_Meta, std::__1::tuple<int,
  
Sanitizer: address (ASAN)

Regressed: https://clusterfuzz.com/revisions?job=linux_asan_chrome_mojo&range=555423:555432

Reproducer Testcase: https://clusterfuzz.com/download?testcase_id=6506050946334720

Issue filed automatically.

See https://github.com/google/clusterfuzz-tools for more information.
 
Project Member

Comment 1 by ClusterFuzz, May 2 2018

Components: Internals>Core
Labels: Test-Predator-Auto-Components
Automatically applying components based on crash stacktrace and information from OWNERS files.

If this is incorrect, please apply the Test-Predator-Wrong-Components label.
Project Member

Comment 2 by ClusterFuzz, May 2 2018

Labels: Test-Predator-Auto-Owner
Owner: adithyas@chromium.org
Status: Assigned (was: Untriaged)
Automatically assigning owner based on suspected regression changelist https://chromium.googlesource.com/chromium/src/+/ca4498823ac5b8947e7752e5cf42bd62dfb07398 (Update SpeechRecognitionSessionConfig to use url::Origin).

If this is incorrect, please let us know why and apply the Test-Predator-Wrong-CLs label. If you aren't the correct owner for this issue, please unassign yourself as soon as possible so it can be re-triaged.
Status: WontFix (was: Assigned)
This uses a client written in javascript to send a StartRequest to the SpeechRecognizer mojo interface implemented by SpeechRecognitionDispatcherHost. Currently we use the old IPCs to reply to the client (which is assumed to be SpeechRecognitionDispatcher in content/renderer) and not the mojo javascript client.
Project Member

Comment 4 by ClusterFuzz, May 10 2018

Labels: Needs-Feedback
ClusterFuzz testcase 6506050946334720 is still reproducing on tip-of-tree build (trunk).

If this testcase was not reproducible locally or unworkable, ignore this notification and we will file another bug soon with hopefully a better and workable testcase.

Otherwise, if this is not intended to be fixed (e.g. this is an intentional crash), please add ClusterFuzz-Ignore label to prevent future bug filing with similar crash stacktrace.
Project Member

Comment 5 by ClusterFuzz, May 15 2018

ClusterFuzz has detected this issue as fixed in range 558327:558329.

Detailed report: https://clusterfuzz.com/testcase?key=6506050946334720

Fuzzer: mojo_fuzzer
Job Type: linux_asan_chrome_mojo
Platform Id: linux

Crash Type: CHECK failure
Crash Address: 
Crash State:
  iter != handle_map_.end() in speech_recognition_dispatcher.cc
  content::SpeechRecognitionDispatcher::OnErrorOccurred
  bool IPC::MessageT<SpeechRecognitionMsg_ErrorOccurred_Meta, std::__1::tuple<int,
  
Sanitizer: address (ASAN)

Regressed: https://clusterfuzz.com/revisions?job=linux_asan_chrome_mojo&range=555423:555432
Fixed: https://clusterfuzz.com/revisions?job=linux_asan_chrome_mojo&range=558327:558329

Reproducer Testcase: https://clusterfuzz.com/download?testcase_id=6506050946334720

See https://github.com/google/clusterfuzz-tools 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