none
Query regarding "NdisFreeCloneOidRequest" in FilterOidRequestComplete in nDIS LWF RRS feed

  • Question

  • Hello,

    I see that after the NdisFreeCloneOidRequest is called in FilterOidRequestComplete, the cloned request is not NULL or not deleted. It still is allocated. When does this cloned request get cleaned up? Will it not cause hanging resource? 

    Also how exactly does NdisFreeCloneOidRequest work? What is it freeing?

    Thanks,

    Rashmi.

    Wednesday, October 12, 2016 5:32 PM

Answers

  • How are you detecting that it is not allocated?   Memory deallocation in Windows does nothing to the existing memory, it just adds it back to a free pool.   So it is possible you will see the request in memory for a long time, but that doesn't mean you can use it.


    Don Burn Windows Driver Consulting Website: http://www.windrvr.com

    • Marked as answer by Rashmi.s Friday, November 4, 2016 7:52 PM
    Thursday, October 13, 2016 1:38 PM

All replies

  • How are you detecting that it is not allocated?   Memory deallocation in Windows does nothing to the existing memory, it just adds it back to a free pool.   So it is possible you will see the request in memory for a long time, but that doesn't mean you can use it.


    Don Burn Windows Driver Consulting Website: http://www.windrvr.com

    • Marked as answer by Rashmi.s Friday, November 4, 2016 7:52 PM
    Thursday, October 13, 2016 1:38 PM
  • I was just checking by putting a breakpoint. I saw that all the fields within the oidRequest structure were still valid and nothing changed. So , is there any way by which I can check if the pointer to this oidRequest is valid or not , in case I want to put a safety check?
    Monday, October 17, 2016 6:44 PM