Update troubleshooting.mdx (#598)

Added a section on how to record a CPU profile to diagnose performance
issues with Cody in VSCode

<!-- Explain the changes introduced in your PR -->

## Pull Request approval

Although pull request approval is not enforced for this repository in
order to reduce friction, merging without a review will generate a
ticket for the docs team to review your changes. So if possible, have
your pull request approved before merging.

Author: Rhia2

docs/cody/troubleshooting.mdx

@@ -123,6 +123,31 @@ Note that you may need to quit VSCode first, then run that command to re-launch
 
 ![](https://gist.github.com/assets/458591/d590636b-31e5-4436-8039-ee62b7a8e59f)
 
+### Record a CPU profile for Cody in VSCode
+
+If you are experiencing performance issues with Cody in VSCode, recording a CPU profile can help diagnose the problem. Here’s how you can capture a CPU profile:
+
+1. **Open Developer Tools**:
+   - In VSCode, go to the Command Palette (`Ctrl+Shift+P` on Windows/Linux, `Cmd+Shift+P` on macOS).
+   - Type `Developer: show running extensions` and select it to open running extensions.
+
+2. **Record the CPU Profile**:
+   - There you should see Cody in the list. Right click on it and start a host profile.
+   - This will show you the running profile in the bottom right of the window.
+   - Reproduce the issue you are experiencing with Cody.
+   - Once you have reproduced the issue, click the message in the bottom right you stop the trace.
+
+3. **Save the CPU Profile**:
+   - After stopping the trace, you need to go back to the Developer: show running extensions view.
+   - Right click Cody and click `Save extension profile`.
+
+4. **Share the CPU Profile**:
+   - Attach the `.cpuprofile` file to your issue report on GitHub or share it with the support team for further analysis.
+
+Following these steps will help the team understand and resolve the performance issues more effectively.
+
+
+
 ## JetBrains IntelliJ extension
 
 ### Access Cody logs