[CP-stable] Disable async mode with LLDB#184983
Merged
auto-submit[bot] merged 3 commits intoApr 15, 2026
Merged
Conversation
|
This pull request was opened from and to a release candidate branch. This should only be done as part of the official Flutter release process. If you are attempting to make a regular contribution to the Flutter project, please close this PR and follow the instructions at Tree Hygiene for detailed instructions on contributing to Flutter. Reviewers: Use caution before merging pull requests to release branches. Ensure the proper procedure has been followed. |
Contributor
There was a problem hiding this comment.
Code Review
This pull request disables LLDB asynchronous mode to address breakpoint rearming issues and updates the expected log pattern from process resumption to breakpoint location addition. Feedback indicates that using breakpoint addition is a weak indicator for workflow initialization and suggests renaming the _lldbProcessResuming variable to better reflect its updated purpose.
Contributor
Author
hellohuanlin
approved these changes
Apr 14, 2026
d8d0a0a
into
flutter:flutter-3.41-candidate.0
132 checks passed
engine-flutter-autoroll
added a commit
to engine-flutter-autoroll/packages
that referenced
this pull request
Apr 16, 2026
engine-flutter-autoroll
added a commit
to engine-flutter-autoroll/packages
that referenced
this pull request
Apr 17, 2026
engine-flutter-autoroll
added a commit
to engine-flutter-autoroll/packages
that referenced
this pull request
Apr 17, 2026
Xbectordash
pushed a commit
to Xbectordash/abhi_flutter_fork
that referenced
this pull request
May 13, 2026
### Issue Link: What is the link to the issue this cherry-pick is addressing? flutter#184254 ### Impact Description: What is the impact (ex. visual jank on Samsung phones, app crash, cannot ship an iOS app)? Does it impact development (ex. flutter doctor crashes when Android Studio is installed), or the shipping of production apps (the app crashes on launch). This information is for domain experts and release engineers to understand the consequences of saying yes or no to the cherry pick. Debugging on physical iOS devices often crashes when using Xcode 26.4. ### Changelog Description: Explain this cherry pick: * In one line that is accessible to most Flutter developers. * That describes the state prior to the fix. * That includes which platforms are impacted. See [best practices](https://github.com/flutter/flutter/blob/main/docs/releases/Hotfix-Documentation-Best-Practices.md) for examples. When debugging on physical iOS devices and Xcode 26.4+, app often crashes. ### Workaround: Is there a workaround for this issue? * Use a simulator * Or launch from Xcode * Or use Xcode 26.3 * Or use a wireless device ### Risk: What is the risk level of this cherry-pick? ### Test Coverage: Are you confident that your fix is well-tested by automated tests? ### Validation Steps: What are the steps to validate that this fix works? Do `flutter run` in https://github.com/flutter/flutter/tree/master/dev/integration_tests/flutter_gallery using Xcode 26.4 and a physical iOS device.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
Issue Link:
What is the link to the issue this cherry-pick is addressing?
#184254
Impact Description:
What is the impact (ex. visual jank on Samsung phones, app crash, cannot ship an iOS app)?
Does it impact development (ex. flutter doctor crashes when Android Studio is installed),
or the shipping of production apps (the app crashes on launch).
This information is for domain experts and release engineers to understand the consequences of saying yes or no to the cherry pick.
Debugging on physical iOS devices often crashes when using Xcode 26.4.
Changelog Description:
Explain this cherry pick:
See best practices for examples.
When debugging on physical iOS devices and Xcode 26.4+, app often crashes.
Workaround:
Is there a workaround for this issue?
Risk:
What is the risk level of this cherry-pick?
Test Coverage:
Are you confident that your fix is well-tested by automated tests?
Validation Steps:
What are the steps to validate that this fix works?
Do
flutter runin https://github.com/flutter/flutter/tree/master/dev/integration_tests/flutter_gallery using Xcode 26.4 and a physical iOS device.