VR: Voice search is broken on ToT (M-66) |
||||
Issue descriptionClicking the voice search button now blows up in the speech recognition system. This is reliably reproducible. [FATAL:chrome_speech_recognition_manager_delegate.cc(280)] Check failed: context.render_process_id != content::ChildProcessHost::kInvalidUniqueID (-1 vs. -1) Stack Trace: RELADDR FUNCTION FILE:LINE 000cfdf9 logging::LogMessage::~LogMessage() /usr/local/google/work/chromium/src/base/logging.cc:581:29 0095ab0d speech::ChromeSpeechRecognitionManagerDelegate::CheckRecognitionIsAllowed(int, base::OnceCallback<void (bool, bool)>) /usr/local/google/work/chromium/src/chrome/browser/speech/chrome_speech_recognition_manager_delegate.cc:279:3 00d2d81d content::SpeechRecognitionManagerImpl::StartSession(int) /usr/local/google/work/chromium/src/content/browser/speech/speech_recognition_manager_impl.cc:155:16 I'm going to take a look when I can, but leaving available for now.
,
Feb 20 2018
This was caused by: https://chromium-review.googlesource.com/c/chromium/src/+/922802
,
Feb 23 2018
Passing to Ian who's volunteered to dig into this.
,
Feb 28 2018
I found another instance of this problem on ChromeOS. The breaking CL has been reverted. We should establish a formal, clear way of allowing speech requests from the browser thread. A separate bug tracks this in issue 817359.
,
Feb 28 2018
Verified that this works with build 66.0.3356.0 canary. |
||||
►
Sign in to add a comment |
||||
Comment 1 by cjgrant@chromium.org
, Feb 20 2018