<?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 Hi Ivan, in Graphics</title>
    <link>https://community.intel.com/t5/Graphics/Memory-leak-caused-by-NV-DX-interop/m-p/1122142#M87669</link>
    <description>&lt;P&gt;Hi Ivan,&lt;/P&gt;

&lt;P&gt;Thanks for the bin and src files it will help with replication. The issue reported and we investigate the problem.&amp;nbsp;&lt;/P&gt;

&lt;P&gt;-Michael&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Tue, 21 Mar 2017 16:41:30 GMT</pubDate>
    <dc:creator>Michael_C_Intel2</dc:creator>
    <dc:date>2017-03-21T16:41:30Z</dc:date>
    <item>
      <title>Memory leak caused by NV_DX_interop</title>
      <link>https://community.intel.com/t5/Graphics/Memory-leak-caused-by-NV-DX-interop/m-p/1122141#M87668</link>
      <description>&lt;P&gt;Hello, I am a developer in AxxonSoft (http://www.axxonsoft.com/)&lt;/P&gt;

&lt;P&gt;We use Intel Quick Sync for video decompression and then NV_DX_interop extension to share Direct3D textures with our OpenGL renderer. It seems that NV_DX_interop gives a memory leak on Intel NUC platforms. Memory leaks after creating Direct3D render target, calling wglDXRegisterObjectNV/wglDXUnregisterObjectNV on it and releasing this render target. It happens both in 64 bit and 32 bit applications.&lt;/P&gt;

&lt;P&gt;System Setup Information:&lt;BR /&gt;
	-----------------------------------------&lt;/P&gt;

&lt;P&gt;System Used: Intel® NUC NUC6I5SYK&lt;BR /&gt;
	CPU SKU: Intel Core i5-6260U&lt;BR /&gt;
	GPU SKU: Intel Iris 540&lt;BR /&gt;
	Processor Line: N/A&lt;BR /&gt;
	System BIOS Version: N/A&lt;BR /&gt;
	CMOS settings: N/A&lt;BR /&gt;
	Graphics Driver Version: 21.20.16.4590&lt;BR /&gt;
	GOP/VBIOS Version: N/A&lt;BR /&gt;
	Operating System: Windows&lt;BR /&gt;
	OS Version: Windows 7 Professional x64&lt;BR /&gt;
	API: OpenGL extension NV_DX_interop&lt;BR /&gt;
	Occurs on non-Intel GPUs?: No, tested on NVIDIA&lt;/P&gt;

&lt;P&gt;&amp;nbsp;&lt;/P&gt;

&lt;P&gt;Steps to Reproduce:&lt;BR /&gt;
	-------------------------------&lt;BR /&gt;
	1. Launch the test program: DXInteropLeak.exe&lt;BR /&gt;
	2. Open the task manager and look for the DXInteropLeak.exe process, note its memory consumption&lt;/P&gt;

&lt;P&gt;&amp;nbsp;&lt;/P&gt;

&lt;P&gt;Expected Results:&lt;BR /&gt;
	-------------------------------&lt;/P&gt;

&lt;P&gt;Process memory is more or less stable all the time.&lt;/P&gt;

&lt;P&gt;&amp;nbsp;&lt;/P&gt;

&lt;P&gt;Actual Results:&lt;BR /&gt;
	-------------------------------&lt;/P&gt;

&lt;P&gt;Process memory is constantly increasing, it takes several seconds to leak 1GB.&lt;/P&gt;

&lt;P&gt;&amp;nbsp;&lt;/P&gt;

&lt;P&gt;Additional Information:&lt;/P&gt;

&lt;P&gt;Power plan set to High Performance. Please note that the problem cannot be reproduced on Intel i5-3570K CPU (HD Graphics 4000, driver 10.18.10.4425). Also problem disappears after commenting lines with wglDXRegisterObjectNV/wglDXUnregisterObjectNV out. Also problem doesn't occur on NVidia GPUs. Looks similar to this bug &lt;A href="https://software.intel.com/en-us/node/707697" target="_blank"&gt;https://software.intel.com/en-us/node/707697&lt;/A&gt;, but leak caused by other NV_DX_interop functions.&lt;/P&gt;</description>
      <pubDate>Fri, 17 Mar 2017 12:33:48 GMT</pubDate>
      <guid>https://community.intel.com/t5/Graphics/Memory-leak-caused-by-NV-DX-interop/m-p/1122141#M87668</guid>
      <dc:creator>Ivan_K_1</dc:creator>
      <dc:date>2017-03-17T12:33:48Z</dc:date>
    </item>
    <item>
      <title>Hi Ivan,</title>
      <link>https://community.intel.com/t5/Graphics/Memory-leak-caused-by-NV-DX-interop/m-p/1122142#M87669</link>
      <description>&lt;P&gt;Hi Ivan,&lt;/P&gt;

&lt;P&gt;Thanks for the bin and src files it will help with replication. The issue reported and we investigate the problem.&amp;nbsp;&lt;/P&gt;

&lt;P&gt;-Michael&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 21 Mar 2017 16:41:30 GMT</pubDate>
      <guid>https://community.intel.com/t5/Graphics/Memory-leak-caused-by-NV-DX-interop/m-p/1122142#M87669</guid>
      <dc:creator>Michael_C_Intel2</dc:creator>
      <dc:date>2017-03-21T16:41:30Z</dc:date>
    </item>
    <item>
      <title>Hi Ivan,</title>
      <link>https://community.intel.com/t5/Graphics/Memory-leak-caused-by-NV-DX-interop/m-p/1122143#M87670</link>
      <description>&lt;P style="font-size: 13.008px;"&gt;Hi Ivan,&lt;/P&gt;

&lt;P style="font-size: 13.008px;"&gt;We have found the root cause and are fixing the issue. Your test case was very helpful in finding the cause. The fix should be included in the next graphics drivers release.&lt;/P&gt;

&lt;P style="font-size: 13.008px;"&gt;-Michael&amp;nbsp;&lt;/P&gt;

&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 30 Mar 2017 14:28:15 GMT</pubDate>
      <guid>https://community.intel.com/t5/Graphics/Memory-leak-caused-by-NV-DX-interop/m-p/1122143#M87670</guid>
      <dc:creator>Michael_C_Intel2</dc:creator>
      <dc:date>2017-03-30T14:28:15Z</dc:date>
    </item>
    <item>
      <title>Hi Michael,</title>
      <link>https://community.intel.com/t5/Graphics/Memory-leak-caused-by-NV-DX-interop/m-p/1122144#M87671</link>
      <description>&lt;P&gt;Hi Michael,&lt;/P&gt;

&lt;P&gt;Glad to hear it. Thank you.&lt;/P&gt;</description>
      <pubDate>Thu, 30 Mar 2017 15:00:14 GMT</pubDate>
      <guid>https://community.intel.com/t5/Graphics/Memory-leak-caused-by-NV-DX-interop/m-p/1122144#M87671</guid>
      <dc:creator>Ivan_K_1</dc:creator>
      <dc:date>2017-03-30T15:00:14Z</dc:date>
    </item>
    <item>
      <title>Hello,</title>
      <link>https://community.intel.com/t5/Graphics/Memory-leak-caused-by-NV-DX-interop/m-p/1122145#M87672</link>
      <description>&lt;P&gt;Hello,&lt;/P&gt;

&lt;P&gt;the memory leak is fixed in the 6 and 7 generation &lt;SPAN class="short_text" id="result_box" lang="en"&gt;&lt;SPAN&gt;processors with the new driver.&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/P&gt;

&lt;P&gt;&lt;SPAN class="short_text" id="result_box" lang="en"&gt;&lt;SPAN&gt;Will this also be fixed in the 3, 4 and 5 generation?&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Wed, 17 May 2017 06:58:20 GMT</pubDate>
      <guid>https://community.intel.com/t5/Graphics/Memory-leak-caused-by-NV-DX-interop/m-p/1122145#M87672</guid>
      <dc:creator>Markus_B_1</dc:creator>
      <dc:date>2017-05-17T06:58:20Z</dc:date>
    </item>
    <item>
      <title>H Markus,</title>
      <link>https://community.intel.com/t5/Graphics/Memory-leak-caused-by-NV-DX-interop/m-p/1122146#M87673</link>
      <description>&lt;P&gt;H Markus,&lt;/P&gt;

&lt;P&gt;Since we the fix if a new driver is released supporting 3rd, 4th, or 5th generation the fix will be included.&amp;nbsp;&lt;/P&gt;

&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 18 May 2017 21:03:39 GMT</pubDate>
      <guid>https://community.intel.com/t5/Graphics/Memory-leak-caused-by-NV-DX-interop/m-p/1122146#M87673</guid>
      <dc:creator>Michael_C_Intel2</dc:creator>
      <dc:date>2017-05-18T21:03:39Z</dc:date>
    </item>
  </channel>
</rss>

