|
|
Performance problems are tricky to diagnose, but you can help by providing a sample. This is also useful if you get a beachball.
|
|
|
|
|
|
### For Mac OS X 10.9 and later
|
|
|
There are two ways to get a sample. You can use Activity Monitor or run `/usr/bin/sample`.
|
|
|
|
|
|
## Activity Monitor
|
|
|
|
|
|
1. Open activity monitor (in /Applications/Utilities)
|
|
|
2. Select iTerm2 in the list of processes
|
|
|
3. Click the "i" button
|
|
|
|
|
|
![Small-I](https://gitlab.com/gnachman/iterm2/uploads/29dcc745ba82b230c6dad53aa4cc762b/Small-I.png)
|
|
|
![Screen_Shot_2021-10-29_at_11.24.41_AM](uploads/bfd93909444ee3bffa82de5da445fb03/Screen_Shot_2021-10-29_at_11.24.41_AM.png)
|
|
|
|
|
|
4. Click the "Sample" button
|
|
|
5. Save the result and attach it to the issue.
|
|
|
|
|
|
### For Mac OS X 10.8 and earlier
|
|
|
1. Open /Applications/Utilities/Activity Monitor
|
|
|
2. Select iTerm
|
|
|
3. Press "Sample process"
|
|
|
4. Save the file and attach it to a [http://code.google.com/p/iterm2/issues/entry new issue] or existing issue. |
|
|
\ No newline at end of file |
|
|
## /usr/bin/sample
|
|
|
|
|
|
Activity Monitor can be tricky if your performance problem is short lived. You can capture a sample at the command line (either in iTerm2 or Terminal.app) by running `/usr/bin/sample $PID > sample.txt` where `$PID` is the process ID of the main iTerm2 process. You can use Activity Monitor to find the process ID by searching for `iTerm2` and use the value from the `PID` column. |