Chrome Version: 57.0.2987.85 beta / CRD version 61.0.3163.20
OS: ChromeOS Kevin
What steps will reproduce the problem?
(1) Launch Chrome Remote Desktop.
(2) Attempt to connect to a host.
What is the expected result?
Expect to be able to connect to a host.
What happens instead?
CRD reports that a required component failed. If you keep re-trying, it eventually says that some components are missing.
In the JS console, logging indicates that the NaCl component is crashing, e.g:
plugin dimensions:748x918
main.html:1 [.PPAPIContext]GL ERROR :GL_INVALID_ENUM : ScopedTextureBinder::dtor: <- error from previous GL command
main.html:1 NativeClient: NaCl module crashed
console_wrapper.js:115 Connection dropped: ERROR_NACL_PLUGIN_CRASHED client_session.js:677
remoting.ConsoleWrapper.recordAndLog_ @ console_wrapper.js:115
remoting.ClientSession.notifyStateChanges_ @ client_session.js:677
remoting.ClientSession.setState_ @ client_session.js:589
remoting.ClientSession.onConnectionStatusUpdate @ client_session.js:515
remoting.ClientPluginImpl.onPluginCrashed_ @ client_plugin_impl.js:186
ui_mode.js:123 App mode: home.client.connect-failed.me2me
console_wrapper.js:115 NaCl Module crashed. client_plugin_impl.js:193
remoting.ConsoleWrapper.recordAndLog_ @ console_wrapper.js:115
remoting.ClientPluginImpl.onPluginCrashed_ @ client_plugin_impl.js:193
ui_mode.js:123 App mode: home
Comment 1 by w...@chromium.org
, Oct 8 2017