Re: WMI Leaks?
From: [MS] Scott McNairy (scotmc_at_online.microsoft.com)
Date: 07/23/04
- Previous message: Troy Jerkins: "ASP.NET and WMI"
- Messages sorted by: [ date ] [ thread ]
Date: Fri, 23 Jul 2004 15:03:51 -0700
I meant to say that there are "no known issues"
-- [MS] Scott McNairy WMI Test Engineer This posting is provided "As Is" with no warranties, and confers no rights. Use of included script samples are subject to the terms specified at http://www.microsoft.com/info/cpyright.htm From: "[MS] Scott McNairy" <scotmc@online.microsoft.com> Subject: Re: WMI Leaks ? Date: Friday, July 23, 2004 11:21 AM There are any known issues, given that the one gateway to WMI is via this method, there would have been a lot of complaints by now. I am not aware of any Service Pack fixes to IWbemLocator::ConnectServer call. -- [MS] Scott McNairy WMI Test Engineer This posting is provided "As Is" with no warranties, and confers no rights. Use of included script samples are subject to the terms specified at http://www.microsoft.com/info/cpyright.htm "Manjunath" <manjunath.d@gmail.com> wrote in message news:3db5ab73.0407230557.274600de@posting.google.com... > Hi Scott, > > I feel that memory leaks are not because of my code. The cleanup > operation under different failure cases has been tested and under all > cases, I release the allocated memory and call co-unitialize. > > I have had peer-review done on code. Just to be sure ;-) > > Please let me know if there are any issues of WMI or DCOM or COM+ > leaking memory under specific conditions. > > If there was no any issues, please let me know the Service pack that > provided the fix or if the bug is still open. > > > Thanks > > Manjunath
- Previous message: Troy Jerkins: "ASP.NET and WMI"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|