Hi,
I'm doing a lot of DisconnectController/ConnectController against
gEfiSimpleFileSystemProtocolGuid and that's working fine, but I saw huge
memory leaks 4M on virtualbox 500K on physical machine, etc.. For a test I
stopped all/most of that but left the program end left part that will
locate Block Io protocol, keep all the handles/device paths that relate to
an actual device (no media paths), then ran through and disconnect
controller on those handles then use LocateDevicePath to try and find a
match (using gEfiDevicePathProtocolGuid because Block IO is now gone and
LocateDevicePath will fail) which it finds the old handle again, I then
call connectcontroller(handle, NULL, leftoverlocatedpath, TRUE) on it. It
all works, but there are big memory leaks, they go away if I simply comment
out the disconnect and connect calls. I also tried a method of opening
application EXCLUSIVE the block io handle, closing it, then calling
connectcontroller(handle, NULL, NULL, TRUE) and that also seems to work but
still has big memory leaks.
Is there something I should need to do to prevent those or is it more
likely implementation issues or the drivers?
TIA!!
------------------------------------------------------------------------------
LIMITED TIME SALE - Full Year of Microsoft Training For Just $49.99!
1,500+ hours of tutorials including VisualStudio 2012, Windows 8, SharePoint
2013, SQL 2012, MVC 4, more. BEST VALUE: New Multi-Library Power Pack includes
Mobile, Cloud, Java, and UX Design. Lowest price ever! Ends 9/20/13.
http://pubads.g.doubleclick.net/gampad/clk?id=58041151&iu=/4140/ostg.clktrk
_______________________________________________
edk2-devel mailing list
edk2-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/edk2-devel
