View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0012698 | MMW v4 | Other | public | 2015-04-08 11:15 | 2015-05-14 15:49 |
| Reporter | Ludek | Assigned To | |||
| Priority | urgent | Severity | minor | Reproducibility | have not tried |
| Status | closed | Resolution | fixed | ||
| Product Version | 4.1.6 | ||||
| Target Version | 4.1.7 | Fixed in Version | 4.1.8 | ||
| Summary | 0012698: MediaMonkey64Helper.exe is launched with bInheritHandles set to TRUE (and leaks handles) | ||||
| Description | It would appear that MediaMonkey64Helper.exe is launched with bInheritHandles set to TRUE. This can cause handles not being closed. For example, some plugins use Windows sockets which then stay open even after properly closing them because their handles have been duplicated. Apparently winsock handles cannot be set to be non-inheritable. The issue goes away if I prevent the helper process from running or patch the call to CreateProcess s.t. bInheritHandles is FALSE. | ||||
| Additional Information | #CUG-755-87891 http://www.mediamonkey.com/forum/viewtopic.php?f=7&t=80263 | ||||
| Tags | No tags attached. | ||||
| Fixed in build | 1744 | ||||
|
|
Fixed in 4.1.7.1739 (set the bInheritHandles param to FALSE) https://msdn.microsoft.com/en-us/library/windows/desktop/ms682425(v=vs.85).aspx |
|
|
Verified 1739 |
|
|
Forum user indicates it isn't resolved. |
|
|
The original problem is resolved, user is referring the leaking handles issue, looking into it... |
|
|
The handle leaking issue is fixed in build 4.1.8.1744 |
|
|
Verified 1744 No regressions found Close after user verification |
|
|
Closed, confirmed by user |
