PaintImage can be backed by a PaintRecord, via PaintImageBuilder::set_paint_record. However, PaintRecord-backed PaintImages are also not serialized at the moment.
One option might be to store these PaintRecords in the transfer cache, but PaintRecords themselves might have PaintImages that need to be in the cache, so that dependency tree might get messy.
Another option is to change the code to remove PaintRecord-backed PaintImages and only use PaintRecord-backed PaintShaders in these cases, which should be equivalent.
See also: issue 8063
13, where non-lazy SkImage-backed PaintImages are also not serialized.
PaintImage can be backed by a PaintRecord, via PaintImageBuilder::set_paint_record. However, PaintRecord-backed PaintImages are also not serialized at the moment.
One option might be to store these PaintRecords in the transfer cache, but PaintRecords themselves might have PaintImages that need to be in the cache, so that dependency tree might get messy.
Another option is to change the code to remove PaintRecord-backed PaintImages and only use PaintRecord-backed PaintShaders in these cases, which should be equivalent.
See also: issue 806313 , where non-lazy SkImage-backed PaintImages are also not serialized.
PaintImage can be backed by a PaintRecord, via PaintImageBuilder::set_paint_record. However, PaintRecord-backed PaintImages are also not serialized at the moment.
One option might be to store these PaintRecords in the transfer cache, but PaintRecords themselves might have PaintImages that need to be in the cache, so that dependency tree might get messy.
Another option is to change the code to remove PaintRecord-backed PaintImages and only use PaintRecord-backed PaintShaders in these cases, which should be equivalent.
See also: issue 806313 , where non-lazy SkImage-backed PaintImages are also not serialized.
Comment 1 by khushals...@chromium.org
, Feb 8 2018