Currently, oop raster can be requested by the client but the GrContext can fail to be created in the service.
See: https://cs.chromium.org/chromium/src/gpu/command_buffer/service/gles2_cmd_decoder.cc?sq=package:chromium&l=3794
This makes it complicated to know whether or not oop raster is on or not (see issue 785008 ) and I think will muddy the waters of any finch trial if sometimes it gets turned off. It would be quite nice if we could make this always succeed when requested (assuming that it only is requested when ganesh would be requested).
The essential problem here is that Skia and Chrome maintain different blacklists. Skia may fail to create a GrContext while Chrome thinks it is ok to do so.
Looking for answers from piman/bsalomon here in terms of design ideas. piman suggested offhand that maybe we need to add a capabilities "correctness fuzzer" to make sure that Skia and Chrome always agree. Maybe there's some way to expose/share this code as well.
Comment 1 by piman@chromium.org
, Nov 18 2017Owner: piman@chromium.org