I use VSCode when working on contributions to flutter/flutter. In my typical daily workflow, I frequently switch what branch I'm working on. For example, I might test existing behavior on master. Then I switch back to my feature branch. Then I might switch to someone else's PR branch so that I can review their changes locally. Etc.

I frequently find that this puts Dart-Code into a bad state. Either the Dart analyzer or the Flutter daemon may crash. Sometimes this happens quickly. Sometimes this doesn't happen until X minutes later when I try to navigate to a symbol definition. This nature of these issues make them difficult to pin down or repro.

This issue is tracking my on-going to effort to pin these down and get these filed appropriately. If this issue goes stale without any activity, please close it.

My acceptance criterion for this issue being resolved is this: I would like VSCode to gracefully handle any sort of git switch that I may do on my checkout of Flutter. At most, I should have to do reload my VSCode no more than once after switching commits/branches.