Answered by:
Memory leak from Intel IPP lib

Question
-
I have an application uses Intel IPP to do some image processing, but there are some memory leak,
when use Windbg to analyze the heap, there are two IPP functions allocate lots of memory after a period of running.
the problems are:
1. we didn't call the functions directly,
2. Intel engineer do not want to expose the reference of the funcions.
3. It's hard to reproduce the issue with demo, since we used more than 100 IPP funcations , cannot test one by one
I submitd the issue to Intel, they start to use the word "false postive"
what can I do now?
- Moved by Helen Zhao Wednesday, July 18, 2012 6:37 AM Intel Ipp lib issue (From:Visual C++ General)
Tuesday, July 17, 2012 2:18 PM
Answers
-
Hi xhuan8,
I suggest you move to Intel® Software Network for more helpful ideas about this issue. And this thread will be moved to Off-Topic Posts.
Thanks for your understanding.
Best regards,Helen Zhao [MSFT]
MSDN Community Support | Feedback to us
- Marked as answer by xhuan8 Wednesday, July 18, 2012 1:51 PM
Wednesday, July 18, 2012 6:37 AM
All replies
-
0:014> !heap -p -a 00000000ab38aa60
address 00000000ab38aa60 found
in
_HEAP @ 1e300000
HEAP_ENTRY Size Prev Flags UserPtr UserSize -
state
00000000ab38aa50 00a9 0000 [07] 00000000ab38aa60 00a58 -
(busy)
Trace: 73b1
77edc3d6
ntdll!RtlAllocateHeap+0x0000000000001292
1e2c46c7
ippcore_7_0!ippGetLibVersion+0x0000000000000137
1e2c1cc5
ippcore_7_0!ippMalloc+0x0000000000000015
21ca0da8
ippdcu8_7_0!ippsVLCEncodeOne_16s1u+0x0000000000038658
21c6dd80
ippdcu8_7_0!ippsVLCEncodeOne_16s1u+0x0000000000005630
6427f6005f7
mscorwks!DoNDirectCall__PatchGetThreadCall+0x000000000000007b
642803bc909
+0x00000642803bc909Tuesday, July 17, 2012 2:19 PM -
0:149> !heap -p -a 00000001e9fe69a0
address 00000001e9fe69a0 found
in
_HEAP @ 20fb0000
HEAP_ENTRY Size Prev Flags UserPtr UserSize -
state
00000001e9fe69a0 0035 0000 [07] 00000001e9fe69b0 00320 -
(busy)
Trace: 798d
77edca76
ntdll!RtlAllocateHeap+0x0000000000001292
20e72667
libiomp5md!_kmp_reap_worker+0x0000000000002e57
20e20b16
libiomp5md!kmpc_free+0x0000000000001096
20e654a9
libiomp5md!_kmpc_omp_taskwait+0x0000000000000619
20e4a9d0
libiomp5md!_kmp_fork_call+0x0000000000006e40
20e44a50
libiomp5md!_kmp_fork_call+0x0000000000000ec0
20e27601
libiomp5md!_kmpc_fork_call+0x0000000000000081
22d7508e
ippcvy8_7_0!ippibFastArctan_32f+0x000000000011a62e
6427f601b47
mscorwks!IEE+0x000000000000a8e7
642803e0405 +0x00000642803e0405Tuesday, July 17, 2012 2:19 PM -
Hi xhuan8,
I suggest you move to Intel® Software Network for more helpful ideas about this issue. And this thread will be moved to Off-Topic Posts.
Thanks for your understanding.
Best regards,Helen Zhao [MSFT]
MSDN Community Support | Feedback to us
- Marked as answer by xhuan8 Wednesday, July 18, 2012 1:51 PM
Wednesday, July 18, 2012 6:37 AM