Cody Rank comments

Results 16 comments of


                                            Cody Rank

NaCl crashes on Windows in Chrome 52.0.2743.116 m (64-bit)

I get Nexe crashes too, running chrome 62.0.3202.62 on win 10 64 v1703, regular mosh-chrome and (dev)

NaCl crashes on Windows in Chrome 52.0.2743.116 m (64-bit)

sure. nexe crashes there too: ``` NativeClient: Nexe crashed during startup nassh_command_instance.js:875 loading plugin failed ProgressEvent errorHandler @ nassh_command_instance.js:875 ```

NaCl crashes on Windows in Chrome 52.0.2743.116 m (64-bit)

https://bugs.chromium.org/p/chromium/issues/detail?id=130793 ?

NaCl crashes on Windows in Chrome 52.0.2743.116 m (64-bit)

Okay, I got a workaround that might offer a clue. It works if I open EMET and disable Data Execution Prevention for chrome.exe.

NaCl crashes on Windows in Chrome 52.0.2743.116 m (64-bit)

Thanks, I didn't know about chrome apps dropping windows support. I switched to the native windows version. I have to turn off DEP for that too, but that seems better...

NaCl crashes on Windows in Chrome 52.0.2743.116 m (64-bit)

Here's the entry I added: ![mosh_nw](https://user-images.githubusercontent.com/753031/32201430-4a0a938c-bd94-11e7-8248-b6e0d9acac4d.png)

Make crashes obvious to the user

Thanks for the FAQ tip. I missed that. I'm not sure if this is my problem, but here's what's in my console after trying to connect: ``` init: hterm mosh_window.html:1...

Make crashes obvious to the user

pull request: https://github.com/rpwoodbu/mosh-chrome/pull/161 didn't fix my issue, but now I don't get the error in the log :/

Make crashes obvious to the user

Nope, not on ARM. Plain ol' x86-64. I've tried the dev version as well and get the same Nexe crash.

`asdf plugin add` should exit code 0 in most cases

Totally agree. At least give us an option (e.g. similar to [`--failure-exit-code` in rspec](https://relishapp.com/rspec/rspec-core/docs/command-line/failure-exit-code-option-exit-status))