From 10662f08428710ab432a33401dbfda67fda9f390 Mon Sep 17 00:00:00 2001 From: dan Date: Fri, 22 Nov 2024 11:37:45 +0000 Subject: [PATCH] Update profiling.md --- docs/profiling.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/profiling.md b/docs/profiling.md index 554919a1e75..bd19ffa1aec 100644 --- a/docs/profiling.md +++ b/docs/profiling.md @@ -131,7 +131,7 @@ If the problem seems to be on the native side, you can use the [CPU hotspot prof :::info Choose the Java/Kotlin recording -Make sure you select "Find CPU Hotspots **(Java/Kotlin Recording)**" rather than "Find CPU Hotspots (Callstack Sample)". They have similar icons so it's easy to get confused between them. +Make sure you select "Find CPU Hotspots **(Java/Kotlin Recording)**" rather than "Find CPU Hotspots (Callstack Sample)". They have similar icons but do different things. ::: Perform the interactions and press "Stop recording". Recording is resource-intensive, so keep the interaction short. You can then either inspect the resulting trace in the Android Studio or export it and open it in an online tool like [Firefox Profiler](https://profiler.firefox.com/).