# Only Troubleshooting Report
In heap dump analysis, the heap report is divided into two main sections: the Troubleshooting Report and the Performance Report. The troubleshooting report is helpful for diagnosing issues like memory leaks in your application, while the performance report provides insights for optimizing your application's performance.
By default, the tool analyzes your heap dump file to populate both these sections in the heap report. However, this process can consume additional memory and time, as the tool needs to parse the heap dump file to extract information for both troubleshooting and performance analyses.
In case your interest lies solely in the troubleshooting aspect and you prefer to view only the troubleshooting report section within the heap report, you have the option to configure it. This configuration restricts the display to the troubleshooting report alone, streamlining your focus on pinpointing issues like memory leaks
# yCrash Enterprise Edition
Here are the steps to configure the flag in yCrash Enterprise Edition:
Open the launch file: If you're using a Unix-based machine, open the
launch-yc-server.shfile. For Windows machines, use thelaunch-yc-server.batfile.Add flag: Modify your launch file to include the
-DonlyTroubleshootingReport=truesystem property. For example,java -Xms2g -Xmx4g -DlogDir=. -DuploadDir=. -DonlyTroubleshootingReport=true ...1Restart yCrash server: Save the changes to your launch file and restart the yCrash server to apply the updates.
# yCrash Cloud
Here are the steps to configure the flag in yCrash Cloud:
Coming Soon…