Intel® Inspector User Guide for Windows* OS

ID 767798
Date 3/22/2024
Public

A newer version of this document is available. Customers should click here to go to the newest version.

Document Table of Contents

Troubleshooting Out-of-memory Conditions

Symptoms

  • Intel Inspector displays an out-of-memory message.

  • Intel Inspector stops application execution and collection (with or without reporting an out-of-memory message).

  • In the Windows Task Manager window, the memory used by the application approaches the process limit before application execution stops.

Details

Both the application and the Intel Inspector run in the same address space.

This means the memory footprint of the application running with the Intel Inspector is larger than the memory footprint of the application running without the Intel Inspector, because the Intel Inspector itself consumes memory to detect errors in the application.

Intel Inspector exhibits the symptoms above if the total memory consumed by application and the Intel Inspector is close to or exceeds the total process virtual space.

Possible Correction Strategies

Reduce the amount of work the Intel Inspector must perform during inspection. For example:

  • Use a smaller data set.

  • Inspect the application multiple times and exclude a different set of modules each time.

  • Use OMP_NUM_THREADS to limit the number of threads when inspecting OpenMP* applications. In most cases, OMP_NUM_THREADS=2 is sufficient.