From 324ce85d58a7725e2a8d23b6d94a49e4967b5f5a Mon Sep 17 00:00:00 2001 From: Derek Xu Date: Tue, 5 Aug 2025 11:24:41 -0400 Subject: [PATCH] Document the `--profile-startup` Dart / Flutter CLI flags --- src/content/tools/devtools/cpu-profiler.md | 8 ++++++-- 1 file changed, 6 insertions(+), 2 deletions(-) diff --git a/src/content/tools/devtools/cpu-profiler.md b/src/content/tools/devtools/cpu-profiler.md index 385d1a3c676..826e5a3a68c 100644 --- a/src/content/tools/devtools/cpu-profiler.md +++ b/src/content/tools/devtools/cpu-profiler.md @@ -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