![]() ![]() Review dumps(optional for self analysis): *The idea is to capture dumps so that when comparing dumps side by side, there is a very noticeable difference in memory size. On hitting OOM or when memory has grown very large (1 dump).Gradual increase in the memory (2 dumps at certain intervals).During initial run of the application (1 dump).At least 15 min after the start of the application (1 dump).Note - Dumps should be collected as follows: After every X/4 minutes right click the process and choose "Create Full Userdump". Let the process be monitored for the entire growth period (say some X minutes).It is suggested the process runs for a minimum of 15 minutes with the tracking DLL in place in order to get valid results. After choosing this option, let the process run and leak memory.Locate the process (process id) that is suspected to be leaking memory, Right click the process and choose "Monitor For Leaks". In the main window, activate the Processes tab.Start DebugDiag Collection: Start->All Programs->Debug Diagnostics Tool ->DebugDiag Collection.Click OK to save and close the Dialog box.select the option: Record call stacks immediately when monitoring for leaks.select the option: Use fixed initial folder for data files.select the option: Include source and line information in analysis report.Enter the path where you want to save the userdumps under - Manual Userdump Save Folder.Go to Tools->Options and Settings., which brings up a dialog box.Įnter the following text under Folders and Search Paths->Symbol Search Path for Debugging: To configure the symbol path that Debug Diagnostic Tool uses for Debugging:.Click "Cancel" on the "Select Rule Type" Dialog Box. ![]() Start DebugDiag Collection: Start->All Programs->Debug Diagnostics Tool->DebugDiag Collection.Note: Replace with the actual path where the JRE is installed.This is required to give the path for all the JRE PDB files so that DebugDiag can pick up the necessary JRE symbols. Use the Microsoft Symbol Server to obtain debug symbol files To configure the symbol path that DebugDiag uses:įor more information about symbol tables see:.Select the option: Save reports in relative subfolders when possible. Start DebugDiag Analysis: Start->All Programs->Debug Diagnostics Tool ->DebugDiag Analysis. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |