For OopAsh the ash process will be the VizHost. Currently viz/gpu are heavily tied with content. In order to convert --mash to --oop-ash we need a way for Ash to start viz. For the short term it's fine to have ash use content for this. Long term viz/gpu should be refactored out of content. This bug is to provide a way for Ash to start viz/gpu (in process).
Comment 1 by zalcorn@chromium.org
, May 25 2018