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
Following code will cause a crash if you set a breakpoint in the break statement and start debugging (ignore what the code is doing, it is just a simplified sample code to reproduce the crash):
Future<void> test() async {
for (int i =0; i <2; i++) {
if (i >0) {
break;
}
awaitFuture.delayed(Duration(seconds:1));
}
}
Few observations:
both the break and the await statements are required for the crash to occur
there is no crash if the breakpoint is removed
it won't crash if you replace the break statement with a continue statement
Crash log (there is some unrelated stuff in the log because I tested this inside my actual app):
The text was updated successfully, but these errors were encountered:
kinex
changed the title
Crash if setting a breakpoint in a break statement of a for loop
Crash if setting a breakpoint to the break statement of a for loop
Apr 13, 2019
The issue has been fixed in the SDK. I've verified it with the current nightly build 👍 It will take a little while to make stable builds of Dart/Flutter though.
Following code will cause a crash if you set a breakpoint in the
break
statement and start debugging (ignore what the code is doing, it is just a simplified sample code to reproduce the crash):Few observations:
break
and theawait
statements are required for the crash to occurbreak
statement with acontinue
statementCrash log (there is some unrelated stuff in the log because I tested this inside my actual app):
The text was updated successfully, but these errors were encountered: