flutter_flutter

mirror of https://github.com/flutter/flutter.git synced 2026-02-20 02:29:02 +08:00

History

Dan Field b763483b43 [Impeller] Do not reference this in the submit callback for Metal GPU Surfaces (flutter/engine#50361 )

Fixes https://github.com/flutter/flutter/issues/141351 (speculatively - I have not directly reproduced this in an application, but without this change the added test crashes with a segfault in the submit callback).

If the rasterizer gets torn down, the surface gets released and the submit callback may fire on a collected object. Capturing `this` isn't safe. I'm not quite sure how that could happen from the linked stack trace though, since the draw call and the teardown call should be happening on the raster thread, and if the surface was reset then the draw call should've failed earlier...

The added test causes a segfault without the change.

2024-02-05 20:58:17 +00:00

common

[Impeller] make GPU tracing off by default. (flutter/engine#50215 )

2024-02-01 00:55:33 +00:00

gpu

[Impeller] Do not reference this in the submit callback for Metal GPU Surfaces (flutter/engine#50361 )

2024-02-05 20:58:17 +00:00

platform

Revert "[Fuchsia] Execute most of the testing/fuchsia/test_suites.yaml on debug and release builds" (flutter/engine#50291 )

2024-02-02 11:40:10 -08:00

profiling

Enforce consistent stack size for Flutter threads (flutter/engine#49111 )