Ignoring Analysis Issues

The issues that the memory analyser reports are not always something that need to be corrected. For example, the analyser will present issues related to instances that are only kept alive by delegates. Even though this can indicate a memory problem that can cause a memory leak, it can also be perfectly legitimate to have instances that are only kept alive by a delegate. If the issue is not an actual problem, if the information it presents is not needed, or if the issue cannot be corrected for some reason (e.g. it is caused by the framework or third party code), it might be a good idea to ignore the issue so that it will no longer be presented.

An issue is ignored by clicking the (Ignore...) link next to the issue title, which will bring up the Ignore Analysis Issue window. This window is used to define when the issue should be ignored. The available options are:

• Always ignore this issue
  The issue will always be ignored, regardless of the type, instance, or call stack associated with the issue.

• Only ignore issue for the type <type name>
  Only ignore issue for selected types
  The issue will be ignored based on the type associated with the issue. If no types are associated with the issue, this option is not available. If more than one type is available, a type selector will be included in the window.

• Only ignore issue when root path contains selected fields and methods
  The issue will be ignored based on the root path of the instance. If no instance is associated with the issue, this option is not available. If this option is selected, a root path selector will be included in the window. The root path selector can be used to select fields and methods that must exist in a root path in order for the issue to be ignored.

• Only ignore issue when... (based on allocation)
  The issue will be ignored based on the allocation call stack. If no allocation call stack is associated with the issue, this option is not available. If this option is selected, an allocation selector will be included in the window. The allocation selector is described below.

• Only ignore for the instance #xxx

  Only ignore for selected instances
  The issue will only be ignored for specific instances. If more than one instance is available an instance selector will be included in the window

It is possible to select more than option, in which case all options must be met for the issue to be ignored.

Allocation selector

The allocation selector is used to specify how an issue should be ignored based on the allocation call stack. This selector is shown if the Only ignore issue when... option is selected. The available options are:

• Allocated by <method name>
  Allocated by selected methods
  The issue will only be ignored if the selected method is at the top of the allocation call stack. If more than one method is available, a method selector will be included in the window.

• Allocated by selected call stack methods
  The issue will only be ignored if the selected methods is at the top of the allocation call stack. If this option is selected, a call stacks methods selector will be included in the window. The call stacks methods selector can be used to select a call stack and then one or more methods at the top of the call stack.

• Allocation stack contains selected methods
  The issue will only be ignored if the allocation call stack contains the selected methods. If this option is selected, a call stacks methods selector will be included in the window. The call stacks methods selector can be used to select a call stack and then one or more methods within the call stack.

Ignore issue in

The Ignore issue in dropdown list is used to define where the information about the ignored issue should be stored. The available options are:

• All sessions
  The ignored issue will be stored as a default ignored issue. It will be ignored in all profiling sessions.

• Profiler project (Professional and Enterprise only)
  The ignored issue will be stored in the profiler project associated with the session. It will be ignored in all profiling sessions associated with the same project. This option is only available if the session is associated with a profiler project.

• Current session
  The ignored issue will be stored in the current profiler session. It will only be ignored in this session.