Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[CP-stable]Add a check for the surface if it is valid #56301

Conversation

flutteractionsbot
Copy link

@flutteractionsbot flutteractionsbot commented Nov 1, 2024

This pull request is created by automatic cherry pick workflow

Issue Link:

flutter/flutter#155018

Changelog Description:

Summary:

A crash in Flutter SDK 3.24.1 affects Android apps using PlatformView, not limited to Google Maps. The crash occurs when the surface is released unexpectedly, causing subsequent draw calls to fail.

Impact Description:

Summary:
A crash in Flutter SDK 3.24.3 affects Android apps using PlatformView, not limited to Google Maps. The crash occurs when the surface is released unexpectedly, causing subsequent draw calls to fail.

Impact:
This issue can lead to app crashes on Android for any PlatformView usage, affecting stability across a range of widgets and plugins that rely on native views.

Workaround:

Is there a workaround for this issue?

Release the Surface in a regular way might avoid the issue, per flutter/flutter#155018 (comment)

Risk:

What is the risk level of this cherry-pick?

  • Low
  • Medium
  • High

Test Coverage:

Are you confident that your fix is well-tested by automated tests?

  • Yes
  • No

Validation Steps:

What are the steps to validate that this fix works?

Fixes an issue where the Surface is not valid and the `draw` method is crashing.

flutter/flutter#155018

[C++, Objective-C, Java style guides]: https://github.com/flutter/engine/blob/main/CONTRIBUTING.md#style
@flutteractionsbot flutteractionsbot added the cp: review add the cp request to the review queue of release engineers label Nov 1, 2024
@flutteractionsbot
Copy link
Author

@AlexV525 please fill out the PR description above, afterwards the release team will review this request.

@reidbaker
Copy link
Contributor

I am approving but if @jonahwilliams disagrees then his opinion should take weight over mine.

Copy link
Member

@jonahwilliams jonahwilliams left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Change seems safe enough.

LGTM

@eyebrowsoffire eyebrowsoffire added the autosubmit Merge PR when tree becomes green via auto submit App label Nov 12, 2024
@auto-submit auto-submit bot merged commit c21a11e into flutter:flutter-3.24-candidate.0 Nov 12, 2024
27 checks passed
@auto-submit auto-submit bot removed the autosubmit Merge PR when tree becomes green via auto submit App label Nov 12, 2024
@AlexV525
Copy link
Member

Should I request a CP for the framework? Does any automatic workflow manage it?

@reidbaker
Copy link
Contributor

@AlexV525 the engine changes to this branch will automatically be rolled in by the release engineer. Who is @eyebrowsoffire for this release.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
cp: review add the cp request to the review queue of release engineers platform-android
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants