Observed Memory Leak Issue When Running OpenVINO™ Image Classification Async C++ Sample

• Ran OpenVINO™ Image Classification Async C++ Sample by executing the _CrtMemDumpAllObjectsSince method.
• Detected memory leak as below:

  Dumping objects ->{253771} normal block at 0x000001BAE43B8700, 112 bytes long.Data: <@ ; 0 ; > 40 8F 3B E4 BA 01 00 00 30 98 3B E4 BA 01 00 00{253770} normal block at 0x000001BAE43B9830, 112 bytes long.Data: < ; @ ; > 00 87 3B E4 BA 01 00 00 40 8F 3B E4 BA 01 00 00{253769} normal block at 0x000001BAE31B4590, 128 bytes long.Data: <@ ; @ ; > 40 8F 3B E4 BA 01 00 00 40 8F 3B E4 BA 01 00 00{253768} normal block at 0x000001BAE3218760, 16 bytes long.Data: < v > 00 76 80 08 F8 7F 00 00 00 00 00 00 00 00 00 00{253767} normal block at 0x000001BAE43B8F40, 112 bytes long.Data: <0 ; ; > 30 98 3B E4 BA 01 00 00 00 87 3B E4 BA 01 00 00{253766} normal block at 0x000001BAE32173B0, 16 bytes long.Data: < u > E8 75 80 08 F8 7F 00 00 00 00 00 00 00 00 00 00  : Object dump complete.

CrtDumpMemoryLeaks() reports all objects that weren't destroyed (global objects too). So, they were able to reproduce the issue by including openvino/openvino.hpp only (without any execution in main), or with DEFINE... macro from gflags library (used by sample) without OpenVINO™ at all. According to the analysis above, such a report can't be treated as a real product memory leak.

Use sanitizers or valgrind tools as more reliable tools to check memory leakage.

More details about how to track memory leaks may be found in Optimizing memory usage