The picture may hold references to images backed by GPU textures that must
be deleted on the IO thread.

At some point recently we started putting a JSON file in the out/ directory and this broke this suggested build script.
This patch makes the script more resilient to such files.

Allow checkerboarding raster cache entries for debugging purposes (can be toggled from Dart). (#3200)

(JSONObject.getString() will return the string "null" for a JSON null value)

Fixes https://github.com/flutter/flutter/issues/6643

This is to ensure that the depfile generated by the snapshotter has
the correct target.

Update DartServiceIsolate/FlutterView because VMServiceIO_NotifyServerState
now provides a URI for the observatory

Initialize AndroidSurfaceGL and its associated resource context before ANativeWindow acquisition. (#3193)

* Initialize AndroidSurfaceGL and its associated resource context before ANativeWindow acquisition.

This allows us to create the IO thread context way earlier and service load requests on the same. Before this patch, early lifecycle loads would use the default Skia texture loader instead of the Async texture loader we provide.

Fixes https://github.com/flutter/flutter/issues/6581

* Don't destroy surface_gl_ PlatformViewAndroid::ReleaseSurface.

An SkPicture may hold a reference to an SkImage backed by a GL texture.
The GL texture is associated with the resource context bound to the IO
thread and must be deleted through that context.

Fixes #6496

The RenderView destructor does not delete its descendants.
RenderObject::destroy must be called to delete the object tree along with
other cleanup tasks.

Also associate a CustomFontData with dynamically loaded fonts in order to get
the desired FontDataCache behavior at RenderObject::destroy time.

After this patch, we no longer link with Mojo. We still use some gn definitions
from //mojo to create Dart packages.

We had a typo in our decoding logic.

Fixes https://github.com/flutter/flutter/issues/6564

We no longer use mojom to transport messages. We still use the Mojo EDK
to spin the event loop, however.

Now they all flow through some common routines.

Now we just pass the data directly.

Causes warnings in Xcode.