michaelsadoff
commented
4 years ago The memory leak occurs because the Get-WinEvent cmdlet doesn't clean up properly. To work around the issue, replace all Get-WinEvent lines in the script with direct calls to the EventLogReader class and run the EventLogReader.Dispose method after. For example, replace the following line:
$taskIgnoredEvent = Get-WinEvent -LogName 'Microsoft-Windows-TaskScheduler/Operational' -FilterXPath $ignoredXPath -MaxEvents 1 -ErrorAction SilentlyContinue
With:
$query = New-Object -TypeName System.Diagnostics.Eventing.Reader.EventLogQuery -ArgumentList @('Microsoft-Windows-TaskScheduler/Operational', 1, $ignoredXPath) $reader = New-Object -TypeName System.Diagnostics.Eventing.Reader.EventLogReader -ArgumentList $eventquery $taskIgnoredEvent = $reader.ReadEvent() $reader.Dispose()
scherndl
BCornelissen
There is a memory usage problem in this managemantpack.
In our enviroment, we saw that the monitoring agents memory usage is growing and growing.
I found that the problem is in this MP, exactly in the GetTaskAndJobsProperties_2.ps1 script.
The cmdlet get-winevent with the parameter MaxEvents do not give the used memory free.
get-winevent -LogName 'Microsoft-Windows-TaskScheduler/Operational' -FilterXPath $successXPath -MaxEvents 1My first solution was to fix it with
get-winevent -LogName 'Microsoft-Windows-TaskScheduler/Operational' -FilterXPath $successXPath | Select-Object -First 1But there is the same bug...
My next try was
(get-winevent -LogName 'Microsoft-Windows-TaskScheduler/Operational' -FilterXPath $successXPath)[0]This works, as a workaround, but needs much much more time...
I am not sure if the problem exists in every OS, you can quickly check it if you try:
while(1) {get-winevent -LogName 'System' -MaxEvents 1 | Out-Null}and the look at the memory usage of the PS process. I tried it on (2012R2, 2019, Win10)@rafabu thx for sharing this great MP