I observed that a loop on below powershell command will cause the memory usage steadily increase:

Write-EventLog -LogName $logName -Source $sourceName -Message "perfLog" -EventId 0 -EntryType information

Does Write-EventLog have memory leak? Or there is any resource cleanup call that I missed? Thanks for any clue.

• Edited by Leonjl Monday, June 01, 2015 3:33 PM
• Moved by Franklin ChenMicrosoft contingent staff Tuesday, June 02, 2015 11:51 AM Powershell

There are 4 jobs which matches the number of cores on my computer.

The sleep is to control the event generation rate and simulate different system loads caused by event generation. Thanks.

• Edited by Leonjl Tuesday, June 02, 2015 4:19 PM

The memory usage stabilize when most memory is used (15G). The system is already very slow because of this. 

• Edited by Leonjl Wednesday, June 03, 2015 1:54 PM

I am not (and don't need) using a lot of jobs. I only use 4 jobs on a 4 core with 15G memory - which is a decent machine for windows. This has nothing to do with the heaviness of the jobs. If I remove the sleep, the jobs are heavier and the memory used is much less and stable. Obviously sleep is the trouble maker. If start-sleep is not friendly, is there other way to introduce waiting in powershell? Thanks.

• Edited by Leonjl Wednesday, June 03, 2015 6:08 PM

Start-Sleep does not have a -ms option, try changing to -milliseconds (or -m), see if that makes a difference.  I suspect what is happening is that the error info from all the failed start-sleeps is consuming memory.

• Edited by RichardEmptage Wednesday, June 03, 2015 2:31 PM
• Proposed as answer by jrv Wednesday, June 03, 2015 2:58 PM

Using -milliseconds does not solve the problem.

• Edited by Leonjl Wednesday, June 03, 2015 5:03 PM

Problem solved: 

http://stackoverflow.com/questions/30671343/start-sleep-memory-leak-or-causing-powershell-memory-leak

• Edited by Leonjl 15 hours 33 minutes ago
• Marked as answer by Leonjl 15 hours 33 minutes ago

Problem solved: 

http://stackoverflow.com/questions/30671343/start-sleep-memory-leak-or-causing-powershell-memory-leak

• Edited by Leonjl 15 hours 25 minutes ago
• Marked as answer by Leonjl 15 hours 25 minutes ago

So the problem was bad code and not a memory leak or bug. 

Problem solved: 

http://stackoverflow.com/questions/30671343/start-sleep-memory-leak-or-causing-powershell-memory-leak

• Edited by Leonjl Saturday, June 06, 2015 3:36 PM
• Marked as answer by Leonjl Saturday, June 06, 2015 3:36 PM