Ride 4 crashes on start-up

[DyalogRichard]

RIDE Issue Report

Describe the issue you are having

Ride 4 crashes on start-up. If started from e.g. the command-line, it outputs lots of messages of the form

[11667:0317/095913:ERROR:gles2_cmd_decoder.cc(2291)] [.RenderWorker-0x1074c2e9aa00]GL ERROR :GL_INVALID_ENUM : GLES2DecoderImpl::DoBindTexImage2DCHROMIUM: <- error from previous GL command
[11667:0317/095913:ERROR:gles2_cmd_decoder.cc(2295)] [.RenderWorker-0x1074c2e9aa00]GL ERROR :GL_INVALID_OPERATION : ScopedTextureBinder::ctor: was unhandled

Disabling 3D graphics support in my VM is a workaround. Jay said:

"It seems like a problem with the Chromium engine using the GPU to do its rendering, and maybe some bad interaction with your VM.

Other people have reported similar things in Chrome and Electron, e.g.:
http://askubuntu.com/questions/836616/chromium-crashes-upon-starting-in-ubuntu-16-04"

Did you connect to an already running interpreter or start the interpreter from RIDE?

N/A - unable to get that far.

How do you reproduce the issue?

Just start RIDE 4

Paste the contents of Help → About (Shift+F1)

IDE:
Version: 4.0.2745
Platform: Linux x86_64
Date: 2017-03-16 14:13:05 +0000
Git commit: 9094f07
Preferences:{
"dbg":"1",
"wse":"1"
}

Interpreter:
Version: unknown
Platform: unknown
Edition: unknown
Date: unknown

[jayfoad]

Disabling 3D graphics support in my VM is a workaround.

Another workaround, if you're starting RIDE from the command line, is to add --disable-gpu.

It looks like upstream Chromium has a workaround for the bug too.