Dear Michael,
Unfortunately the bug is not fixed on Intel Hardware (XPS 13 9360, Intel
HD Graphics 620 (Kaby Lake GT2)), chromium keeps flooding the log with
the vsync errors.
I have tried you chromium 69 build from experimental, the libgles2
package is installed.
The option --use-gl=osmesa makes the error go away, but gives:
[16317:16317:0904/130327.506076:ERROR:gl_implementation.cc(291)] Failed
to load /usr/lib/chromium/libosmesa.so: /usr/lib/chromium/libosmesa.so:
cannot open shared object file: No such file or directory
[16317:16317:0904/130327.526413:ERROR:viz_main_impl.cc(235)] Exiting GPU
process due to errors during initialization
[16276:16276:0904/130327.985332:ERROR:gpu_process_transport_factory.cc(1007)]
Lost UI shared context.
[48:55:0904/130328.084620:ERROR:command_buffer_proxy_impl.cc(111)]
ContextResult::kFatalFailure: Shared memory region is not valid
[5:895:0904/130340.659249:ERROR:adm_helpers.cc(73)] Failed to query
stereo recording.
[16276:16276:0904/130400.832395:ERROR:latency_info.cc(144)]
Surface::TakeLatencyInfoFromFrame, LatencyInfo vector size 101 is too big.
Looking forward to hearing back from you!
