VR uses a speech recognition session from within the browser process, but SpeechRecognitionManager was designed for use in render processes.  There is at least one other instance, on ChromeOS.

Recently, a DCHECK was added to ensure SpeechRecognitionSessionContext has a valid render_process_id.  This broke the browser-process cases, where kInvalidUniqueID was intentionally specified.

The breaking CL has been reverted.  The original was:

https://chromium-review.googlesource.com/c/chromium/src/+/922802

Before re-enabling the checks, we need to come up with a cleaner way to indicate "intentionally no render_process_id".