-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
VM crash when debugging (watch) #49430
Comments
Same issue without using My problem goes away with the following versions:
The issue persists with Flutter 3.0.1 when Flutter and Dart extensions are on 3.44.0. |
To whom it is helpful: here is crash dump created with Flutter 3.0.5 on Android arm64 (host: macOS 12.5, VS Code with Flutter v3.46 and Dart v3.46.1 extensions): Is it created using these instructions. |
This might be fixed already by 6970e09. If so, would it be feasible to port the fix to Dart 2.17? |
//cc @itsjustkevin there is a question about cherry picking a fix to the Dart 2.17 release. I would think we are very close to a Dart 2.18 stable release and maybe we could have the user upgrade to Dart 2.18. |
@a-siva There is a bit of risk in cherry-picking this late into the cycle. Is this a major issue that needs to be taken care of now or can it wait for a stable hotfix? |
@itsjustkevin the user was asking about cherry picking into the Dart 2.17 release. The fix already exists in Dart 2.18 |
@athomas is it reasonable to do a stable and beta hotfix next week? |
Yes, we can do that.
…On Fri, 19 Aug 2022, 14:51 Kevin Chisholm, ***@***.***> wrote:
@athomas <https://github.com/athomas> is it reasonable to do a stable and
beta hotfix next week?
—
Reply to this email directly, view it on GitHub
<#49430 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AEYRJBZNNMKLZIE3Z6QBYHTVZ57NBANCNFSM53EAYS2A>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
Discussed offline with @mraleph and @mkustermann: hotfix approved for 2.17 based on low risk and user impact. |
This is a patch release that: - Fixes a crash in the debugger (issue [#49430][]). [#49430]: #49430 Bug: #49430 Change-Id: I9b1e4f7422be502a08ab7f199effed3e799311ca Reviewed-on: https://dart-review.googlesource.com/c/sdk/+/255985 Commit-Queue: William Hesse <whesse@google.com> Reviewed-by: Alexander Thomas <athom@google.com>
This has been cherry-picked to the 2.17.7 stable patch release. |
How can I manually upgrade the dart SDK in the flutter SDK? |
I some situations you could theoretically do that, but this fix requires rebuilding Flutter Engine binaries. Unless you are familiar with the process, I'd recommend waiting for this fix to be released as part of the normal Flutter release process (or upgrade to the Flutter channel which contains the fix). |
The Flutter app crashes when I try to inspect (watch) a value with the debugger.
A simple way to reproduce this can be found here: marcglasberg/fast_immutable_collections#42
By following the explanation there, I get this stack overflow:
Environment is:
Flutter (Channel stable, 3.0.4, on Microsoft Windows [Version 10.0.19044.1766], locale pt-BR)
I am the author of the https://pub.dev/packages/fast_immutable_collections package, and I was able to easily reproduce this.
There are 2 possibilities:
IList
class has a bug that is being triggered by the debugger. Note the IList is anIterable
, but it's not aList
.Could you please tell me what methods the debugger calls to create the watch?
In any case, the app shouldn't crash like this, in any circumstances. The debugger should catch the error and say something like "this object's inspection throws an error".
The text was updated successfully, but these errors were encountered: