Maybe a bug or very high number of handles opened, please discuss
log in

Advanced search

Message boards : Application Code Discussion : Maybe a bug or very high number of handles opened, please discuss

Author Message
hristo
Send message
Joined: 19 Nov 14
Posts: 3
Credit: 100,819
RAC: 0

Message 64297 - Posted: 4 Feb 2016, 20:49:24 UTC

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. ..."

hristo
Send message
Joined: 19 Nov 14
Posts: 3
Credit: 100,819
RAC: 0

Message 64298 - Posted: 4 Feb 2016, 21:23:49 UTC

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.

phroggie
Send message
Joined: 10 Feb 16
Posts: 1
Credit: 97,394
RAC: 0

Message 64336 - Posted: 15 Feb 2016, 8:53:02 UTC

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: &lt;Unknown type&gt; : 3 &lt;Unknown type&gt; : 2 &lt;Unknown type&gt; : 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:

Mark Hurd
Send message
Joined: 17 Jan 15
Posts: 1
Credit: 3,893,561
RAC: 0

Message 65074 - Posted: 28 Aug 2016, 6:14:59 UTC - in response to Message 64336.

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.
____________


Post to thread

Message boards : Application Code Discussion : Maybe a bug or very high number of handles opened, please discuss


Main page · Your account · Message boards


Copyright © 2018 AstroInformatics Group