Datasets:
Ekhlass
/
flutter_docs

Dataset card Data Studio Files
xet
Community
1
text
stringlengths
1
372
memory leaks, memory bloat, and more. the view
has the following features:
<topic_end>
<topic_start>
expandable chart
the expandable chart provides the following features:
<topic_end>
<topic_start>
memory anatomy
a timeseries graph visualizes the state of
flutter memory at successive intervals of time.
each data point on the chart corresponds to the
timestamp (x-axis) of measured quantities (y-axis)
of the heap. for example, usage, capacity, external,
garbage collection, and resident set size are captured.
<topic_end>
<topic_start>
memory overview chart
the memory overview chart is a timeseries graph
of collected memory statistics. it visually presents
the state of the dart or flutter heap and dart’s
or flutter’s native memory over time.
the chart’s x-axis is a timeline of events (timeseries).
the data plotted in the y-axis all has a timestamp of
when the data was collected. in other words,
it shows the polled state (capacity, used, external,
RSS (resident set size), and GC (garbage collection))
of the memory every 500 ms. this helps provide a live
appearance on the state of the memory as the application is running.
clicking the legend button displays the
collected measurements, symbols, and colors
used to display the data.
the memory size scale y-axis automatically
adjusts to the range of data collected in the
current visible chart range.
the quantities plotted on the y-axis are as follows:
<topic_end>
<topic_start>
profile memory tab
use the profile memory tab to see current memory
allocation by class and memory type. for a
deeper analysis in google sheets or other tools,
download the data in CSV format.
toggle refresh on GC, to see allocation in real time.
<topic_end>
<topic_start>
diff snapshots tab
use the diff snapshots tab to investigate a feature’s
memory management. follow the guidance on the tab
to take snapshots before and after interaction
with the application, and diff the snapshots:
tap the filter classes and packages button,
to narrow the data:
for a deeper analysis in google sheets
or other tools, download the data in CSV format.
<topic_end>
<topic_start>
trace instances tab
use the trace instances tab to investigate what methods
allocate memory for a set of classes during feature execution:
<topic_end>
<topic_start>
bottom up vs call tree view
switch between bottom-up and call tree views
depending on specifics of your tasks.
the call tree view shows the method allocations
for each instance. the view is a top-down representation
of the call stack, meaning that a method can be expanded
to show its callees.
the bottom-up view shows the list of different
call stacks that have allocated the instances.
<topic_end>
<topic_start>
other resources
for more information, check out the following resources:
<topic_end>
<topic_start>
using the debug console
the DevTools debug console allows you to watch an
application’s standard output (stdout),
evaluate expressions for a paused or running
app in debug mode, and analyze inbound and outbound
references for objects.
info note
this page is up to date for DevTools 2.23.0.
the debug console is available from the inspector,
debugger, and memory views.
<topic_end>
<topic_start>
watch application output
the console shows the application’s standard output (stdout):
<topic_end>
<topic_start>
explore inspected widgets
if you click a widget on the inspector screen,
the variable for this widget displays in the console:
<topic_end>
<topic_start>
evaluate expressions
in the console, you can evaluate expressions for a paused