Flutter 3.29 is super slow on Android Studio

[changja88]

Steps to reproduce

Until Flutter version 3.27, Android Studio was usable, but versions 3.29 and above are too slow. In particular, autocomplete and the options triggered by Alt + Enter are so slow that they are practically unusable. Also, the wrap + widget feature sometimes works depending on some unknown criteria, but mostly it does not. I can't believe that Android Studio, the official editor for Flutter development, is at this level.

Actual results

FAST!!!!

Logs

Logs

<!-- Paste your logs here -->

Flutter Doctor output

Doctor output

<!-- Paste your output here -->

[NaikSoftware]

Faced same issue. Tried to optimize analysis options but without big results

[pq]

You may be hitting an issue that we've identified in the analysis server.

See this bug for more details: dart-lang/sdk#60335

(The good news is we've got a fix on the way.)

[lemonderon]

I've also encountered an issue where the Dart analyzer fails to index certain .dart files without any apparent reason. This typically occurs in larger projects and significantly impacts my productivity in Android Studio. Restarting the IDE (not the Dart Analysis Server) usually resolves the problem, but not at all times. Sometimes I need to rename file and repaste its content, yet it is not reliable. I've tried numerous AS versions including the recent Canary ones and the issue is present within all of them.

On dart version prev 3.27 everything worked quite fine (except for sometimes IDE indexing file partially).

Interestingly, while VSCode exhibits slowness, it doesn't completely fail to analyze files or highlight syntax like Android Studio does. The Dart Analysis server output in Android Studio indicates that file analysis completes successfully (all of the expected issues highlighted in Description/Location rows are present), suggesting the issue likely lies with the IDE or Dart plugin integration rather than the analyzer itself.

[pq]

Interesting, thanks! Let's take the continued conversation over to dart-lang/sdk#60335 since the fix is likely to happen on the server/analyzer side.