Skip to content

[3.38] Document the --profile-startup Dart / Flutter CLI flags #12272

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 3 commits into from
Nov 16, 2025
+9 −2
Merged

[3.38] Document the --profile-startup Dart / Flutter CLI flags #12272

Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
324ce85
Document the `--profile-startup` Dart / Flutter CLI flags
derekxu16 Aug 5, 2025
0d28e4a
Merge branch 'main' into document-profile-startup-flag
parlough Nov 16, 2025
087fb39
Adjust formatting and use active voice
parlough Nov 16, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
11 changes: 9 additions & 2 deletions src/content/tools/devtools/cpu-profiler.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -38,8 +38,15 @@ and Flame chart).
To load all available CPU samples without manually
recording and stopping, you can click **Load all CPU samples**,
which pulls all CPU samples that the VM has recorded and
stored in its ring buffer, and then displays those
CPU samples in the profiler views.
stored in its sample buffer and then
displays those CPU samples in the profiler view.

By default, the VM's sample buffer is used as a ring buffer,
meaning that once it has become full, new samples start
overwriting the oldest ones in the buffer.
To make the VM instead discard all samples collected after
the sample buffer has become full,
pass the `--profile-startup` flag to `dart run` or `flutter run`.

### Bottom up

Expand Down