<?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 Re: iLO bug: Integrated Remote Console leaks registry handles [via hp.ilo2.virtdevs.DirectIO.devtype in Server Management - Remote Server Management</title>
    <link>https://community.hpe.com/t5/server-management-remote-server/ilo-bug-integrated-remote-console-leaks-registry-handles-via-hp/m-p/6998768#M8006</link>
    <description>&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;This issue needs further investigation and a case needs to be submitted.&lt;/P&gt;&lt;P&gt;So for further assistance from support, we suggest you to submit a case.&lt;/P&gt;&lt;P&gt;Thanks &amp;amp; Regards,&lt;/P&gt;&lt;P&gt;Divya&lt;/P&gt;</description>
    <pubDate>Mon, 05 Mar 2018 08:48:09 GMT</pubDate>
    <dc:creator>Divya123</dc:creator>
    <dc:date>2018-03-05T08:48:09Z</dc:date>
    <item>
      <title>iLO bug: Integrated Remote Console leaks registry handles [via hp.ilo2.virtdevs.DirectIO.devtype]</title>
      <link>https://community.hpe.com/t5/server-management-remote-server/ilo-bug-integrated-remote-console-leaks-registry-handles-via-hp/m-p/6995962#M7989</link>
      <description>&lt;P&gt;I'm managing a ProLiant DL380e Gen8 with iLO 4 version 2.55 on Windows 10 x64 with 32-bit Java 8 Update 162.&lt;/P&gt;&lt;P&gt;The Integrated Remote Console (launched via Web Start) shows a constant increase in Handles in Task Manager's Details page., leading to system performance degredation over time. (Display of Handles needs to be enabled in Task Manager by right-clicking the table header and choosing "Select columns".)&lt;/P&gt;&lt;P&gt;Examining the program with Process Explorer, and IRC appears to be using a function in the extension DLL cpqma-[xxxxxxx].dll (x = random alphanumeric characters), DLL to retrieve the Count from:&lt;/P&gt;&lt;P&gt;HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Services\Disk\Enum&lt;/P&gt;&lt;P&gt;and then checking the values to see whether the resulting value contains "USBSTOR" (indicating USB storage).&lt;/P&gt;&lt;P&gt;This happens within a call to the method hp.ilo2.virtdevs.DirectIO.devtype(x, x, x).&lt;/P&gt;&lt;P&gt;Unfortunately, once it has read the values from the key from using RegOpenKeyEx and RegQueryValueEx, it doesn't release the key with RegCloseKey. Thus a registry handle is leaked on each call. This should be simple enough to fix - just call RegCloseKey on the handle at the end of the method, if it is successfully opened.&lt;/P&gt;&lt;P&gt;[It is unclear why this operation is bering performed several times a second - this soaks up CPU, and could be more efficient if a trigger on drive insertion/removal was used.]&lt;/P&gt;</description>
      <pubDate>Fri, 02 Feb 2018 21:05:01 GMT</pubDate>
      <guid>https://community.hpe.com/t5/server-management-remote-server/ilo-bug-integrated-remote-console-leaks-registry-handles-via-hp/m-p/6995962#M7989</guid>
      <dc:creator>GreenReaper</dc:creator>
      <dc:date>2018-02-02T21:05:01Z</dc:date>
    </item>
    <item>
      <title>Re: iLO bug: Integrated Remote Console leaks registry handles [via hp.ilo2.virtdevs.DirectIO.devtype</title>
      <link>https://community.hpe.com/t5/server-management-remote-server/ilo-bug-integrated-remote-console-leaks-registry-handles-via-hp/m-p/6998768#M8006</link>
      <description>&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;This issue needs further investigation and a case needs to be submitted.&lt;/P&gt;&lt;P&gt;So for further assistance from support, we suggest you to submit a case.&lt;/P&gt;&lt;P&gt;Thanks &amp;amp; Regards,&lt;/P&gt;&lt;P&gt;Divya&lt;/P&gt;</description>
      <pubDate>Mon, 05 Mar 2018 08:48:09 GMT</pubDate>
      <guid>https://community.hpe.com/t5/server-management-remote-server/ilo-bug-integrated-remote-console-leaks-registry-handles-via-hp/m-p/6998768#M8006</guid>
      <dc:creator>Divya123</dc:creator>
      <dc:date>2018-03-05T08:48:09Z</dc:date>
    </item>
  </channel>
</rss>

