Re: ANY Win32_Printer query leaks ~500kbytes in wmiprvse.exe
- From: "Scott McNairy \(MVP\)" <v-scomcn@xxxxxxxxxxxxxxxxxxxx>
- Date: Fri, 27 Jan 2006 09:26:34 -0800
I can't repro this problem you are describe below is all, not saying it
isn't happening in your scenario.
All the script does below is put the remote server into a loop and does what
you specify to do to repro the problem you have described. I tried again to
reproduce with a few different printers installed and failed to see this
large leak that you described. Do you have SP1 installed on your Win2k3
boxes? Perhaps you can see if the script below reproduces the problem? If
it doesn't we can explore some different settings in the script to obtain
the repro.
Note that you will have to change the line given here:
set svc = getobject("winmgmts:\\Win2k3SP2Server\Root\cimv2")
to reflect the name of your remote WMI server. Say it is "YourServer", the
line would look like this:
set svc = getobject("winmgmts:\\YourServer\Root\cimv2")
I was using TaskMgr.exe to monitor the "Network Service" user context owned
wmiprvse.exe process on the server.
Thanks,
--
Scott McNairy
Microsoft MVP - Windows Server Management Infrastructure
"Jeremy Weatherford" <JeremyWeatherford@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in
message news:96B64D8D-2AF0-4019-B5D4-23930BEC0DAA@xxxxxxxxxxxxxxxx
> Regardless of how complex it is, process size increases by 500kb per query
> until it reaches ~130MB, and WMI queries fail with an error about the
> paging
> file being too small. I would call this incontrovertible evidence of a
> memory leak... do you disagree?
>
> I'm afraid I don't know a Scott -- would you like to elaborate on his
> sample
> diagnostic techniques?
>
> Thanks,
> Jeremy
>
>
> "Sam Hobbs" wrote:
>
>> Use of memory by Windows is much more complex than most of us know about.
>> If
>> you need to investigate use of memory in your system, then there are many
>> useful resources provided by Microsoft for that purpose; especially
>> articles
>> and other documentation. Scott has provided a sample of the type of
>> diagnostic techniques that can be useful.
>>
>>
>> "Jeremy Weatherford" <Jeremy Weatherford@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote
>> in
>> message news:098B2DA0-B4D9-497D-960F-82B155FA2DC6@xxxxxxxxxxxxxxxx
>> > Hello,
>> >
>> > I'd like to use WMI to monitor printer status via Win32_Printer, but
>> > I've
>> > discovered that, at least in our environment, ANY query from
>> > Win32_Printer
>> > class causes the process size of the associated wmiprvse.exe provider
>> > to
>> > jump
>> > by 500k -- and not go down. Repeat the query, leak another 500k.
>> > Obviously,
>> > this is not going to work very well.
>> >
>> > The same problem occurs with:
>> > 1) any query: SELECT *, SELECT Caption, etc.
>> > 2) vbscript and CIM Studio
>> > 3) Both Server 2003 boxes with network printers and my XP box
>> >
>> > What's going on here? Nothing interesting shows up in wbemcore.log
>> > with
>> > Logging=2. I don't know which provider to enable debug logging for to
>> > troubleshoot it further. Any suggestions?
>> >
>> > Thanks,
>> > Jeremy Weatherford
>> > Grace International School
>> > Chiang mai, Thailand
>>
>>
>>
.
- References:
- Re: ANY Win32_Printer query leaks ~500kbytes in wmiprvse.exe
- From: Sam Hobbs
- Re: ANY Win32_Printer query leaks ~500kbytes in wmiprvse.exe
- Prev by Date: Re: Lowest-level method to retrieve MAC address!
- Next by Date: ManagementException: Not Found on a Put() of a new object
- Previous by thread: Re: ANY Win32_Printer query leaks ~500kbytes in wmiprvse.exe
- Next by thread: Re: ANY Win32_Printer query leaks ~500kbytes in wmiprvse.exe
- Index(es):
Relevant Pages
|
