text stringlengths 1 474 |
|---|
whether or not the breakpoint was caught by application code.<topic_end> |
<topic_start> |
Known issues |
When performing a hot restart for a Flutter application, |
user breakpoints are cleared.<topic_end> |
<topic_start> |
Other resources |
For more information on debugging and profiling, see the |
Debugging page. |
<topic_end> |
<topic_start>Using the Logging view |
info Note |
The logging view works with all Flutter and Dart applications.<topic_end> |
<topic_start> |
What is it? |
The logging view displays events from the Dart runtime, |
application frameworks (like Flutter), and application-level |
logging events.<topic_end> |
<topic_start> |
Standard logging events |
By default, the logging view shows:<topic_end> |
<topic_start> |
Logging from your application |
To implement logging in your code, |
see the Logging section in the |
Debugging Flutter apps programmatically |
page.<topic_end> |
<topic_start> |
Clearing logs |
To clear the log entries in the logging view, |
click the Clear logs button.<topic_end> |
<topic_start> |
Other resources |
To learn about different methods of logging |
and how to effectively use DevTools to |
analyze and debug Flutter apps faster, |
check out a guided Logging View tutorial. |
<topic_end> |
<topic_start>Using the app size tool |
<topic_end> |
<topic_start> |
What is it? |
The app size tool allows you to analyze the total size of your app. |
You can view a single snapshot of “size information” |
using the Analysis tab, or compare two different |
snapshots of “size information” using the Diff tab.<topic_end> |
<topic_start> |
What is “size information”? |
“Size information” contains size data for Dart code, |
native code, and non-code elements of your app, |
like the application package, assets and fonts. A “size |
information” file contains data for the total picture |
of your application size.<topic_end> |
<topic_start> |
Dart size information |
The Dart AOT compiler performs tree-shaking on your code |
when compiling your application (profile or release mode |
only—the AOT compiler is not used for debug builds, |
which are JIT compiled). This means that the compiler |
attempts to optimize your app’s size by removing |
pieces of code that are unused or unreachable.After the compiler optimizes your code as much as it can, |
the end result can be summarized as the collection of packages, |
libraries, classes, and functions that exist in the binary output, |
along with their size in bytes. This is the Dart portion of |
“size information” we can analyze in the app size tool to further |
optimize Dart code and track down size issues.<topic_end> |
<topic_start> |
How to use it |
If DevTools is already connected to a running application, |
navigate to the “App Size” tab.If DevTools is not connected to a running application, you can |
access the tool from the landing page that appears once you have launched |
DevTools (see installation instructions).<topic_end> |
<topic_start> |
Analysis tab |
The analysis tab allows you to inspect a single snapshot |
of size information. You can view the hierarchical structure |
of the size data using the treemap and table, |
and you can view code attribution data |
(for example, why a piece of code is included in your compiled |
application) using the dominator tree and call graph.<topic_end> |
<topic_start> |
Loading a size file |
When you open the Analysis tab, you’ll see instructions |
to load an app size file. Drag and drop an app size |
file into the dialog, and click “Analyze Size”.See Generating size files below for information on |
generating size files.<topic_end> |
<topic_start> |
Treemap and table |
The treemap and table show the hierarchical data for your app’s size.<topic_end> |
<topic_start>Using the treemap |
A treemap is a visualization for hierarchical data. |
The space is broken up into rectangles, |
where each rectangle is sized and ordered by some quantitative |
variable (in this case, size in bytes). |
The area of each rectangle is proportional to the size |
the node occupies in the compiled application. Inside |
of each rectangle (call one A), there are additional |
rectangles that exist one level deeper in the data |
hierarchy (children of A).To drill into a cell in the treemap, select the cell. |
This re-roots the tree so that the selected cell becomes |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.