Skip to content

"flutter run --machine --no-devtools" unexpectedly spawns devtools #113179

@DanTup

Description

@DanTup

While trying to track down some leaking processes on Dart-Code's integration tests, I noticed a lot of DevTools instances being spawned unexpectedly.

I can reproduce from the terminal on stable and latest master.

flutter create foo
cd foo
flutter run --machine -d flutter_tester --no-devtools

In another terminal, run

ps -x | grep devtools

In the output, there will be a DevTools instance running:

 2283 ttys001    0:00.26 /Users/danny/Dev/Google/flutter/bin/cache/dart-sdk/bin/dart devtools --no-launch-browser

I'm not yet sure why the processes aren't being cleaned up during my test run (it might be that we're aggressively terminating the DAP instead of gracefully shutting it down) and I'm looking into that, but it seems like these DevTools instances shouldn't be spawned at all.

Metadata

Metadata

Assignees

No one assigned

    Labels

    a: devtoolsDevTools related - suite of performance and debugging toolsfound in release: 3.3Found to occur in 3.3found in release: 3.5Found to occur in 3.5has reproducible stepsThe issue has been confirmed reproducible and is ready to work onr: fixedIssue is closed as already fixed in a newer versiontoolAffects the "flutter" command-line tool. See also t: labels.

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions