Page 1 of 1
Handle leak in mediamonkey64helper.exe
Posted: Mon Mar 16, 2015 9:11 pm
by millirem
MM 4.1.6.1736
The number of handles for this process is consistently increasing at the rate of about 1 every 2 seconds, even when the application is idle.
Re: Handle leak in mediamonkey64helper.exe
Posted: Wed Apr 01, 2015 6:08 am
by mmote
The process is set to inherit handles from the main process, which appears to be causing all sorts of problems...
edit: The increasing handles appear to be a different issue
Re: Handle leak in mediamonkey64helper.exe
Posted: Wed Apr 01, 2015 4:29 pm
by Peke
Are you sure that iPhone is not connected as possible issue could come from leaks in Associated Handles/Modules that helper use in order to support x64 iTunes 12.1+ support and Sync?
I'm not being able to replicate for me it stays on 4 threads and 25 Handles.
Re: Handle leak in mediamonkey64helper.exe
Posted: Wed Apr 08, 2015 6:17 am
by Ludek
Re: Handle leak in mediamonkey64helper.exe
Posted: Wed May 13, 2015 4:30 am
by millirem
Hi,
The issue remains (handle leak slowly and steadily increasing) on my machine in the new 4.1.7.1741 release.
JG Miller
Re: Handle leak in mediamonkey64helper.exe
Posted: Wed May 13, 2015 3:49 pm
by Ludek
millirem wrote:Hi,
The issue remains (handle leak slowly and steadily increasing) on my machine in the new 4.1.7.1741 release.
JG Miller
Do you mean Process Explorer -> MediaMonkey64Helper.exe -> Properties -> Performance -> Handles ?
OK, I will look into it.
@mmote, can you confirm that setting bInheritHandles to FALSE resolved the issues with MonkeyMote plugin (as solved via ticket CUG-755-87891) ?
Re: Handle leak in mediamonkey64helper.exe
Posted: Wed May 13, 2015 4:25 pm
by Ludek
Thanks, the handle leaking issue will be fixed in build 4.1.8.1744 (
http://www.ventismedia.com/mantis/view. ... 698#c42529 )
Re: Handle leak in mediamonkey64helper.exe
Posted: Wed May 13, 2015 7:33 pm
by mmote
Ludek wrote:@mmote, can you confirm that setting bInheritHandles to FALSE resolved the issues with MonkeyMote plugin (as solved via ticket CUG-755-87891) ?
Yes, the problems appear to be gone.