I observe that executable milkyway_nbody_1.54_windows_x86_64__mt.exe produces very large number of handles at 55% more than 220000. But it will probably finish normally.

On windows xp 64 bit

On work unit
2/4/2016 9:00:59 PM | Milkyway@Home | Starting task ps_nbody_1_29_16_orphansim_3_v154_1453826702_173800_1



with text in stderr.txt:
///
<search_application> milkyway_nbody 1.54 Windows x86_64 double OpenMP, Crlibm </search_application>
Using OpenMP 4 max threads on a system with 4 processors
Could not load Ktm32.dll (126): The specified module could not be found.
///


This indicate some application programing problem as suggested in

https://blogs.technet.microsoft.com/markrussinovich/2009/09/29/pushing-the-limits-of-windows-handles/

"...Any process that has more than a ten thousand handles open at any given point in time is likely either poorly designed or has a handle leak, so a limit of 16 million is essentially infinite and can simply help prevent a process with a leak from impacting the rest of the system. ..."

To add

It did finish normally.

For about combine of 8 hours or real 2 hours cpu time.
At 27MB of used memory and

More than 300 000 handles opened.

This is a leak of handles I think.

A mere 33% of the way into ps_nbody_2_10_16_orphan1_1_v154_1453826702_495349 and I'm seeing similar behavior in Windows 10 Pro x64. milkyway_nbody_1.54_windows_x86_64__mt.exe just likes trying to flag trains down (that's a semaphore joke).

D:\Users\phroggie\Desktop: handle -p 8788

Handle v4.0
Copyright (C) 1997-2014 Mark Russinovich
Sysinternals - www.sysinternals.com

   10: File  (---)   C:\ProgramData\BOINC\slots\8
   2C: File  (---)   C:\ProgramData\BOINC\slots\8\stderr.txt
  108: File  (---)   C:\ProgramData\BOINC\slots\8\boinc_lockfile

D:\Users\phroggie\Desktop: handle -p 8788 -s

Handle v4.0
Copyright (C) 1997-2014 Mark Russinovich
Sysinternals - www.sysinternals.com

Handle type summary:
  <Unknown type>  : 3
  <Unknown type>  : 2
  <Unknown type>  : 6
  ALPC Port       : 1
  Desktop         : 1
  Directory       : 2
  Event           : 20
  File            : 8
  IoCompletion    : 2
  IRTimer         : 4
  Key             : 4
  Semaphore       : 548264
  Thread          : 7
  TpWorkerFactory : 2
  WaitCompletionPacket: 5
  WindowStation   : 2
Total handles: 548333

D:\Users\phroggie\Desktop: 

Six months later and I'm seeing the same semaphore handle leak again.

Milkyway_nbody_1.62_windows_x86_64__mt.exe is only running short tasks that last around 5 minutes, but accumulate over 744000 semaphores in that time.

---