@Botao, unless it's a problem with our kernel, the ARM Landing Team can't justify spending time on this problem. It seems to be a problem in Chromium itself, so that is outside our scope unless it is deemed critical by ARM.
@Botao, unless it's a problem with our kernel, the ARM Landing Team can't justify spending time on this problem. It seems to be a problem in Chromium itself, so that is outside our scope unless it is deemed critical by ARM.