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
For Flutter we don't actually have a button to jump to the CPU Profiler, it goes to the Performance page. However I've used the same icon for CPU Profiler (since the Performance page is Flutter-specific) for non-Flutter sessions because I don't want to clutter the toolbar too much (eg. adding CPU Profile also for Flutter) or have to find different icons for "CPU Profiler" vs "Performance".
I was expecting to see the profiler launch in a separate window.
I run a two screen system and would normally move the profiler to a different screen so I can see my full dev environment.
Having the screen embedded in vscode precludes this.
the launcher only opens the cpu profile window.
I was expecting to see the full suite of devtool windows (e.g. the memory profiler).
run a debug session, stop it and then run a second debug session
Click the dev tool button.
The tool shows a menu showing the current and last (stopped) session.
Is this intentional?
If it is then I think the order is incorrect. It shows the older session first which is also highlighted in blue.
If we are going to have both then it should have the current session highlighted and it should probably be the first one in the list.
Nope, that sounds like a bug that the previous session stopping wasn't handled correctly - I'll take a look. Thanks!
I don't seem to be able to repro this. If you still can, could you file a new issue with more details about exactly what you're running, etc. - and whether you see "Exited" in the Debug Console for the first session before this occurs?
Capturing logs (with Dart: Capture Logs and leaving everything except Analysis Server ticked) across both sessions may be useful too. Thanks!