You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The dart analyzer had a bug recently where it would consume all memory.
Relevant issue: #34850
My issue: #34876
I was wondering if the fix had already been integrated into flutter's version of the sdk, as this is still an issue for me. If it has then I can reopen this as an issue on the dart side instead.
[✓] Flutter (Channel master, v0.10.2-pre.23, on Linux, locale en_US.UTF-8)
• Flutter version 0.10.2-pre.23 at /home/dcov/flutter
• Framework revision 0d707f3897 (12 hours ago), 2018-10-21 21:31:43 -0700
• Engine revision 58cdd53f90
• Dart version 2.1.0-dev.7.1.flutter-b99bcfd309
[✓] Android toolchain - develop for Android devices (Android SDK 28.0.2)
• Android SDK at /home/dcov/android
• Android NDK location not configured (optional; useful for native profiling support)
• Platform android-28, build-tools 28.0.2
• ANDROID_HOME = /home/dcov/android
• Java binary at: /opt/android-studio/jre/bin/java
• Java version OpenJDK Runtime Environment (build 1.8.0_152-release-1136-b06)
• All Android licenses accepted.
[✓] Android Studio (version 3.2)
• Android Studio at /opt/android-studio
• Flutter plugin version 29.1.1
• Dart plugin version 181.5656
• Java version OpenJDK Runtime Environment (build 1.8.0_152-release-1136-b06)
[!] Connected device
! No devices available
! Doctor found issues in 1 category.
The text was updated successfully, but these errors were encountered:
I don't think it makes sense to have an extra issue open for that.
It usually takes a few days until a new Dart VM lands in Flutter (depending to the conflicts it causes)
and the issue was fixed 3 days ago and there was a weekend in between.
This thread has been automatically locked since there has not been any recent activity after it was closed. If you are still experiencing a similar issue, please open a new bug, including the output of flutter doctor -v and a minimal reproduction of the issue.
The dart analyzer had a bug recently where it would consume all memory.
Relevant issue: #34850
My issue: #34876
I was wondering if the fix had already been integrated into flutter's version of the sdk, as this is still an issue for me. If it has then I can reopen this as an issue on the dart side instead.
The text was updated successfully, but these errors were encountered: