Skip to content

[3.36] 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

Draft
wants to merge 1 commit into
base: main
Choose a base branch
from
Draft

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

Changes from all commits
Commits
Show all changes
1 commit
Select commit
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
8 changes: 6 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,12 @@ 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 views. 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. The `--profile-startup` flag
can be passed to `dart run` or `flutter run` to make the VM instead discard
all samples collected after the sample buffer has become full.

### Bottom up

Expand Down
Loading