This feature previously was introduced in flutter/engine#23798, but was reverted in flutter/engine#28694. This revert can lead to a 5x to 50x increase of memory usage of secondary engines from a FlutterEngineGroup on Android. The revert happened because the GrDirectContext was unsafely being cleaned up on the platform thread. That threading issue needs to be addressed and tests are needed to bolster the approach.

See also:

1. libEGL : call to OpenGL ES API with no current context (logged once per thread) #87937