IPP 6.1 memory leak in ippiRectStdDev_32f_C1R and omp_get_num_proc

[pete_klostermanflash]

Thanks in advance for any assistance with this question. Previous tests of our application suggested that there were minor memory leaks. The following output from a valgrind run, using v6.1.6.063 on a 64 bit linux box give the following loss reports. I would greatly appreciate any suggestions on how to troubleshoot this. Pete 1,312 bytes in 1 blocks are definitely lost in loss record 60 of 61 at 0x4C2815C: malloc (vg_replace_malloc.c:236) by 0x94CDA55: ___kmp_allocate (in /opt/intel/ipp/6.1.6.063/em64t/sharedlib/libiomp5.so) by 0x94D1A6D: ??? (in /opt/intel/ipp/6.1.6.063/em64t/sharedlib/libiomp5.so) by 0x94CE546: __kmp_serial_initialize (in /opt/intel/ipp/6.1.6.063/em64t/sharedlib/libiomp5.so) by 0x94C0F2D: omp_get_num_procs (in /opt/intel/ipp/6.1.6.063/em64t/sharedlib/libiomp5.so) by 0x917F32C: _init (in /opt/intel/ipp/6.1.6.063/em64t/sharedlib/libippcoreem64t.so.6.1) by 0x400F0D4: _dl_init (dl-init.c:70) by 0x4000B29: ??? (in /lib/ld-2.12.1.so) by 0x1: ??? by 0x7FEFFFFEA: ??? by 0x7FF000006: ??? 2,336 bytes in 1 blocks are definitely lost in loss record 61 of 61 at 0x4C2815C: malloc (vg_replace_malloc.c:236) by 0x94CDA55: ___kmp_allocate (in /opt/intel/ipp/6.1.6.063/em64t/sharedlib/libiomp5.so) by 0x94C9548: __kmp_reserve_threads (in /opt/intel/ipp/6.1.6.063/em64t/sharedlib/libiomp5.so) by 0x94C90F3: __kmp_fork_call (in /opt/intel/ipp/6.1.6.063/em64t/sharedlib/libiomp5.so) by 0x94BE5AC: __kmpc_fork_call (in /opt/intel/ipp/6.1.6.063/em64t/sharedlib/libiomp5.so) by 0x9E22625: ippiRectStdDev_32f_C1R (in /opt/intel/ipp/6.1.6.063/em64t/sharedlib/libippcvu8.so.6.1) by 0x44261E: FindPartsAtScale(HaarClassifierSupport const&, SimpleImageTmpl const&, SimpleImageTmpl const&, float, std::vector >*, std::vector >*) (IPPHaarDetector.cpp:1040) by 0x452472: PartDetectThread::thread() (IPPHaarDetector.cpp:1181) by 0x446029: apThread::thread_(void*) (unix_thread.h:81) by 0x8037970: start_thread (pthread_create.c:304) by 0x8AD292C: clone (clone.S:112)

[pete_klostermanflash]

The valgrind report is attached.