This repository was archived by the owner on Feb 25, 2025. It is now read-only.
Destroy overlay surfaces when the rasterizer is torn down #28894
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
In add-to-app, cached engines allow to reuse existing c++ state. However, this state must be kept in synced with the platform state.
After an activity is destroyed, platform resources like Android views must be released, leaving the cached engine in a bad state when these resources are mapped to state in c++.
Related issues:
flutter/flutter#88880
googleads/googleads-mobile-flutter#265