- System requirements
- Profiler architecture
- Profiler installation
- Uninstall profiler
- Running the profiler
- Profiler activation
- Welcome screen
- Start profiling
- Profiling overhead
- Snapshots
- Solving performance problems
- CPU profiling
- Thread profiling
- Object allocation profiling
- Memory profiling
- Exception profiling
- Telemetry
- Probes: monitor higher level events
- Inspections: automatic recognition of typical problems
- Automatically trigger actions on event
- Automatic deobfuscation
- Summary, automatic deobfuscation
- Filters
- Profiler command line
- Command line tool to control profiling
- Export of profiling results to external formats
- Profiler .NET API
- Profiler HTTP API
- Settings
- Troubleshooting
Troubleshooting
- How to check profiler agent status?
- Which port does the profiler agent use?
- I do not see my application in the Monitor Applications list on Welcome screen
- Enable extended diagnostics to troubleshoot SSH issues
- Not enough disk space for temporary files
- OutOfMemoryError in the profiler UI
- UI rendering issues on Linux: black, pink, corrupted or improperly repainting window
- Wrong icon or font sizes in the profiler UI when using 150% display scale
- Large memory snapshot opens slowly
How to check profiler agent status?
The profiler agent status can always be checked by opening
the URL https://localhost:<agent port> for a local profiled application
or https://<remote host>:<agent port> for a remote profiled application
in a web browser.
The remote application status can be checked this way
if a direct connection was allowed with the help of the agent startup option
listen.
Which port does the profiler agent use?
By default, the profiler agent port is allocated in the range 10001-10010
or a random one is used if all ports in this range are busy.
The port can also be specified explicitly with the startup option
port.
If the profiler agent port is not in the default range 10001-10010,
explicitly specify the port in the connection dialog as host:port.
Please note that agent port is not one of the ports you may use to
communicate with the profiled application or server, like HTTP 8080
or HTTPS 443.
If you are unsure which port is used, look at the profiler agent log.
The profiler agent log file is <user home>/.ynp/log/<application name>-<PID>.log,
where <user home> corresponds to the account under which the profiled application is started.
I do not see my application in the Monitor Applications list on Welcome screen
If the profiled .NET application is missing in Monitor Applications list:
- Ensure the application you want to profile is running. Restart the application if has been shut down. If the application fails to start or terminates abnormally, check the application's output, logs etc. for possible errors.
- If you run your application and profiler UI on the same machine but under different users, please run an application and UI under the same user or start your application with profiler agent. .NET applications running under different user might be missing.
- If you profiler remote application with SSH access discovery method, login with the same SSH user under which your application runs or start your application with profiler agent.
- If the application is up and running, ensure that the network connection is not blocked by a firewall, an antivirus etc. Check both the remote machine side and the local machine side. The profiler agent port must be allowed.
-
If you are profiling a remote application, ensure that startup option
listenis properly configured. By default, for security reasons the profiler agent binds the socket only tolocalhostthat might resolve to127.0.0.1. This disables a remote connection to the agent via external network interfaces, but connection is still possible via port forwarding e.g. an SSH tunnel. If you want to allow connections to the remote application via host and port, you should specify the startup optionlisten=<IP>orlisten=all.
Enable extended diagnostics to troubleshoot SSH issues
To help YourKit support investigate a network connectivity issue,
please enable extended logging by adding -Dyk.ssh.debug=true
to <user home>/.ynp/ui.ini.
Restart the profiler UI to make the changes effective.
Not enough disk space for temporary files
When the profiler opens a memory snapshot, it may create temporary files
in the user's default temporary directory.
If there is not enough disk space in the default directory,
please specify alternate directory with the help of the property
-Dyk.tmp.dir=<directory> in <user home>/.ynp/ui.ini
configuration file.
Restart the profiler UI to make the changes effective.
OutOfMemoryError in the profiler UI
The profiler UI may run out of memory, e.g. while opening huge snapshots.
Huge usually means several gigabytes, but the exact numbers vary in
each particular case, depending on snapshot specifics.
Please increase the -Xmx in <user home>/.ynp/ui.ini
configuration file.
Restart the profiler UI to make the changes effective.
UI rendering issues on Linux: black, pink, corrupted or improperly repainting window
Remote desktop and VNC
You may observe rendering issues like a completely pink or black window,
if you use the profiler UI via remote desktop
or similar software. In this case, please specify the lines
in <user home>/.ynp/ui.ini configuration file:
-Dsun.java2d.xrender=false
-Dsun.java2d.opengl=falseTiling window managers
There may be rendering issues with a tiling window manager like Sway.
Usually it looks like a grey window.
If you are using a tiling window manager, please set the environment variable
_JAVA_AWT_WM_NONREPARENTING before running the profiler UI:
export _JAVA_AWT_WM_NONREPARENTING=1Other painting artifacts
We recommend to specify -Dsun.java2d.opengl=false, if you see
completely black windows, or you experience painting artifacts in texts.
This problem is often caused by the installed video drivers.
Other painting artifacts
We recommend to specify -Dsun.java2d.opengl=false, if you see
completely black windows, or you experience painting artifacts in texts.
This problem is often caused by the installed video drivers.
Wrong icon or font sizes in the profiler UI when using 150% display scale
YourKit .NET Profiler automatically detects appropriate font
and icon sizes to match your display properties.
However, it may not work properly if 150% display scale is used.
If you experience this problem, please specify the following lines
in <user home>/.ynp/ui.ini configuration file:
-Dsun.java2d.uiScale=1
-Dyk.font.name=<font name>
-Dyk.font.size=<font size>Lange memory snapshot opens slowly
Opening a large memory snapshot can sometimes take a lot of time. This is usually because the profiler needs to perform a large number of complex calculations when loading the snapshot. Nevertheless, to speed up the opening of the snapshot, you can use the following solutions:
- While loading a snapshot, try to avoid simultaneous running of other applications which use much memory. Running such applications in parallel increases virtual memory swapping which leads to overall system performance degradation.
- Consider using a machine with more physical memory (RAM) available.