<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Memory leak from ippsVLCEncodeOne in Intel® Integrated Performance Primitives</title>
    <link>https://community.intel.com/t5/Intel-Integrated-Performance/Memory-leak-from-ippsVLCEncodeOne/m-p/797651#M2892</link>
    <description>Hello, &lt;BR /&gt;&lt;BR /&gt;Could you please provide more information about your application? likehowdo the applicationcall IPP and what related functions you had used? &lt;BR /&gt;&lt;BR /&gt;Thanks&lt;BR /&gt;Ying</description>
    <pubDate>Thu, 21 Jun 2012 06:06:48 GMT</pubDate>
    <dc:creator>Ying_H_Intel</dc:creator>
    <dc:date>2012-06-21T06:06:48Z</dc:date>
    <item>
      <title>Memory leak from ippsVLCEncodeOne</title>
      <link>https://community.intel.com/t5/Intel-Integrated-Performance/Memory-leak-from-ippsVLCEncodeOne/m-p/797650#M2891</link>
      <description>Hi,&lt;BR /&gt;&lt;BR /&gt;we have a .NET application has memory leak, the stack shows it comes from the invoke to ippsVLCEncodeOne method, but we didn't call it directly.&lt;BR /&gt;in what kind of scenario it will be called?&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;P&gt;0:014&amp;gt; !heap -p -a 00000000ab38aa60&lt;/P&gt;&lt;P&gt;address 00000000ab38aa60 found in&lt;/P&gt;&lt;P&gt;_HEAP @ 1e300000&lt;/P&gt;&lt;P&gt;HEAP_ENTRY Size Prev Flags UserPtr UserSize - state&lt;/P&gt;&lt;P&gt;00000000ab38aa50 00a9 0000 [07] 00000000ab38aa60 00a58 - (busy)&lt;/P&gt;&lt;P&gt;Trace: 73b1&lt;/P&gt;&lt;P&gt;77edc3d6 ntdll!RtlAllocateHeap+0x0000000000001292&lt;/P&gt;&lt;P&gt;1e2c46c7 ippcore_7_0!ippGetLibVersion+0x0000000000000137&lt;/P&gt;&lt;P&gt;1e2c1cc5 ippcore_7_0!ippMalloc+0x0000000000000015&lt;/P&gt;&lt;P&gt;21ca0da8 ippdcu8_7_0!ippsVLCEncodeOne_16s1u+0x0000000000038658&lt;/P&gt;&lt;P&gt;21c6dd80 ippdcu8_7_0!ippsVLCEncodeOne_16s1u+0x0000000000005630&lt;/P&gt;&lt;P&gt;6427f6005f7 mscorwks!DoNDirectCall__PatchGetThreadCall+0x000000000000007b&lt;/P&gt;&lt;P&gt;642803bc909 +0x00000642803bc909&lt;/P&gt;</description>
      <pubDate>Thu, 21 Jun 2012 03:22:11 GMT</pubDate>
      <guid>https://community.intel.com/t5/Intel-Integrated-Performance/Memory-leak-from-ippsVLCEncodeOne/m-p/797650#M2891</guid>
      <dc:creator>Lamp</dc:creator>
      <dc:date>2012-06-21T03:22:11Z</dc:date>
    </item>
    <item>
      <title>Memory leak from ippsVLCEncodeOne</title>
      <link>https://community.intel.com/t5/Intel-Integrated-Performance/Memory-leak-from-ippsVLCEncodeOne/m-p/797651#M2892</link>
      <description>Hello, &lt;BR /&gt;&lt;BR /&gt;Could you please provide more information about your application? likehowdo the applicationcall IPP and what related functions you had used? &lt;BR /&gt;&lt;BR /&gt;Thanks&lt;BR /&gt;Ying</description>
      <pubDate>Thu, 21 Jun 2012 06:06:48 GMT</pubDate>
      <guid>https://community.intel.com/t5/Intel-Integrated-Performance/Memory-leak-from-ippsVLCEncodeOne/m-p/797651#M2892</guid>
      <dc:creator>Ying_H_Intel</dc:creator>
      <dc:date>2012-06-21T06:06:48Z</dc:date>
    </item>
    <item>
      <title>Memory leak from ippsVLCEncodeOne</title>
      <link>https://community.intel.com/t5/Intel-Integrated-Performance/Memory-leak-from-ippsVLCEncodeOne/m-p/797652#M2893</link>
      <description>Hi,&lt;BR /&gt;&lt;BR /&gt;our c++/cli project call IPP from the DLL, dynamic link.&lt;BR /&gt;&lt;BR /&gt;currently we suspect the problem is come from the compress/decompress code, it's from the IPP demo,&lt;BR /&gt;&lt;BR /&gt;EncodeRLE&lt;BR /&gt;ForwardBWT&lt;BR /&gt;ForwardMTF&lt;BR /&gt;EncodeHuffman</description>
      <pubDate>Thu, 21 Jun 2012 06:23:36 GMT</pubDate>
      <guid>https://community.intel.com/t5/Intel-Integrated-Performance/Memory-leak-from-ippsVLCEncodeOne/m-p/797652#M2893</guid>
      <dc:creator>Lamp</dc:creator>
      <dc:date>2012-06-21T06:23:36Z</dc:date>
    </item>
  </channel>
</rss>

