[Inspector] Infinite loading after a hot restart

[AlexV525]

I was running into frequent infinite loading with my project. It usually happens after a hot restart.

To reproduce with my project:

1. Run main.dart.
2. Open the inspector in the side panel or the web.
3. After being loaded completely, trigger a hot restart.
4. The inspector starts infinite loading.

To stop it, I can only stop & rerun the entry point.

I can 100% reproduce this with a specific project, it doesn't seem to reproduce when I run with other projects.

---

DevTools version: 2.40.3
IDE: IntelliJ-IDEA
Connected Device:
CPU / OS: arm64 (64 bit) android
Connected app type: Flutter native (debug build)
Dart Version: 3.6.2
Flutter Version: 3.27.4 / stable
Framework / Engine: d8a9f9a52e / 82bd5b7209

[elliette]

Hi @AlexV525! Could you provide either the project that this occurs on, or a minimal repro where this occurs if you can't share the project? Thank you!

[AlexV525]

Hi @elliette , I can still see this after upgraded Flutter 3.32, but the behavior is slightly different. Now the loading will persist on every start until I press the refresh button mamually. Unfortunately I believe I cannot share the project because it's an internal one. How can I find useful logs or debugging info? Maybe I can also debug to find the cause too.

[elliette]

Hi @AlexV525 - would you be able to share the output of debugDumpApp for the app this reproduces on? Thanks!

[elliette]

Hi @AlexV525 - a few other things that could help us diagnose this.

1. I see you have "Show implementation widgets" toggled on. Do you also run into this when "Show implementation widgets" is toggled off?

2. If you enable the legacy inspector, click on your app's root widget, navigate to the details view and trigger a hot restart, do you also run into this?

3. Finally, could open up the Chrome DevTools console for Flutter DevTools in your browser and share any logs or errors you see?

Thank you!

[AlexV525]

@elliette Thanks for keeping up.

I've tried all my projects with DevTools version 2.45.1 (likely bundled with Flutter 3.32) to find the reproducible behavior, and it seems to have gone regardless of the options I've switched.

I'm going to close the issue since it seems to be resolved. Thanks for your time.