Chinmay Garde efd2fd46aa Don't depend on an implicit transaction when presenting drawables on the raster thread. (flutter/engine#18076) ...

The way transactions were added changed in
8500bd4156.
This broke rendering using both Metal and OpenGL when no implicit transaction
was present on the transaction stack. The failure models differ based on Metal
vs. OpenGL and iOS/device versions. On older versions of iOS, rendering would
consume memory till exhaustion. On newer iOS versions, rendering would be stuck
(till a timeout). This patch brings transaction management back in line with as
it was earlier and also makes the Metal backend resilient to transactions being
present on the transaction stack at all. Since this is still quite brittle,
transaction management must be moved to IOSSurface as a followup.

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

2020-05-01 13:05:23 -07:00

..

src/flutter

Don't depend on an implicit transaction when presenting drawables on the raster thread. (flutter/engine#18076)

2020-05-01 13:05:23 -07:00