Locate deadlocks & data races: is more detail with a smaller granularity deeper default stack frame depth and configurable scope.
== Different Memory level ==
== Different Memory level ==The three levels for memory error analysis are detect leaks, detect memory problems and locate memory problems.
[[File:MemoryLevels.png|700px]]
The three levels for Detect Leaks: just tracks whether the memory error analysis are allocating gets deallocated. Detect Memory Problems: Expands on detect leaksby also detecting bad interaction of memory such as invalid memory access, as well as enabling real time analysis. Locate Memory Problems: Is similar to detect memory problems but more detailed. With a deeper default stack frame depth and locate guard zones which shows offsets of memory problemsaccesses of allocated blocks.In the inspector the button “Reset Leak Tracking”, stops tracking all currently allocated memory for leaks, discarding associated tracking data without reporting it.The button “Find Leaks” creates a report on the leak status of all currently allocated memory, then stops tracking those blocks. The button “Reset Growth Tracking” discards all currently-tracked memory growth data. Memory currently allocated won’t count towards growth. The button “Measure Growth” creates a report on how much memory usage has grown since the last reset. Does not reset tracking information.
= Pros vs Cons =
