View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0015277 | MMW v4 | Other | public | 2018-12-21 04:57 | 2020-07-15 15:50 |
| Reporter | rusty | Assigned To | |||
| Priority | urgent | Severity | crash | Reproducibility | always |
| Status | resolved | Resolution | won't fix | ||
| Product Version | 4.1.23 | ||||
| Target Version | 4.1.24 | ||||
| Summary | 0015277: MM4 fails to terminate | ||||
| Description | Recently, I noticed that MM 4.1.23 is consistently not terminating on my PC (MediaMonkey.exe is always left running after the other processes terminate). This applies only to my 'regular' installation--when I create a test portable install, MM terminates correctly as one would expect. It's possible (though doubtful) that I wouldn't have noticed this at release, so I suspect that it may have to do with MM5 testing of 14890. I think--though i'm not certain, that this behavior began when I'd installed MM5 as a 'normal' build, and after doing so, I'd uninstalled MM4 (accidentally), MM5, and then re-installed MM4 using the existing settings and DB. Can you have a look at these logs to see if it looks like a bug in MM4 OR if it appears that MM5 might somehow have corrupted MM4 config settings? | ||||
| Tags | No tags attached. | ||||
| Attached Files | |||||
| Fixed in build | |||||
|
|
Based on the debug log it looks that MM4 has finished correctly. 1) Are you sure that it was MM4 process and not MM5 process? MM5 runs more processes and some are called the same (Mediamonkey.exe) 2) Are you sure that it was not process started by the MediaMonkeyService ? i.e. ensure that the service is uninstalled in Options > Media Sharing Also, go to services and ensure that 'MediaMonkey Serivice' is not there. 3) Download this MediaMonkey.exe : https://www.dropbox.com/sh/rfa3vk2lg26w1eq/AADIFI1Yy1Skg4gNxYzu6_Bva?dl=0 and replace it over your current C:\Program Files (x86)\MediaMonkey\MediaMonkey.exe and generate new debug log using it. I added more debug messages to the app finalization code (to see more) |
|
|
1) I restarted my machine and then ran MM4 to be certain that no MM5 processes were involved. Same result. 2) Confirmed: no MediaMonkey service is running 3) I generated new logs with both the original mediamonkey.exe and the new custom one. Interestingly, MM terminated properly with the new one! fwiw, I wonder whether it could be related to: a) hpcde driver (since in the log provided yesterday, it appeared as if leaving a CD inserted caused hpcde to not terminate) b) testing of case 3D at #14890 (I had installed MM5 non-portable--perhaps that caused problems) c) 0012838 since when I'd installed MM4 (after accidentally uninstalling it) I'd noticed a process like MM~2477.exe, though that has never happened again) On the other hand, none of these hypotheses explain why the custom MediaMonkey.exe solves the problem (unless it includes new hpcde code). |
|
|
It really does not make much sense that the new custom EXE supplied by me works (while the EXE from 1881 does not work). There was nothing except for the debug messages added. 4) You indicated that if you install 1881 to another folder as portable then it closes properly, right? Could you try to install 1881 to another folder as normal (non-potable) build, e.g. to C:\Program Files (x86)\MediaMonkey 1881\ to see whether it works then? 5) Could you try to disable your anti-virus software to see whether it has impact on the issue? 6) if 4&5 isn't going to shed some light on this then Petr should try to create 4.1.24.1882 to see whether the issue will exist in 1882 too, if yes, then it will be something in the installer (or building process) that somehow marks (or makes) the EXE non-close-able for you. |
|
|
4) The problem didn't occur when installing to a differnt directory (except at first install: ME~4262.exe would remain running. Upon uninstalling and re-installing to /MediaMonkey, the exact same as above occurred (i.e. the original problem didn't happen). I'll try testing more tomrrrw night. |
|
|
I don't think that ME~4262.exe is our process, I don't see any such a process on my machine. I guess that your anti-virus software or a third party software/service on your machine creates the process. Could you see which location it has in Properties (right-click the process > Properties) But better would be to use ProcessExplorer > Properties > Image like this: https://www.dropbox.com/s/vrmss2hbszqg5ke/Screenshot%202018-12-22%2015.55.34.png?dl=0 to see more about the process. Also, try to disable your AV software to see whether AV isn't creating this "dummy" process. |
|
|
With MM 4.1.29 on this particular Dell machine, a runtime error is now occurring each time MM is closed. Such errors don't occur with any other apps, but they also don't occur with MM on any other machines, so I'm not sure what the problem is. In any case, it's probably not worth spending any time on this. |
