View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0018987 | MMW 5 | Other | public | 2022-04-18 22:38 | 2022-05-01 23:34 |
| Reporter | peke | Assigned To | |||
| Priority | urgent | Severity | major | Reproducibility | unable to reproduce |
| Status | closed | Resolution | fixed | ||
| Target Version | 5.0.3 | Fixed in Version | 5.0.3 | ||
| Summary | 0018987: MM5 start crashes started MM4 (on certain conditions) | ||||
| Description | MM5 start closes started MM4 (regression). MM5 Log file sent offline. | ||||
| Tags | No tags attached. | ||||
| Fixed in build | 2617 | ||||
|
|
I cannot replicate and I don't see how this could happen. Also in the sent log I don't see a debug messages about MM4 closing, there are messages about MM5 close later only. The last message from MM4 process was: 00015048 35.34806061 [12552] Win7Tools - Thumbnail - add rating stars Questions: 1) Are you really sure that MM4 process was closed ? i.e. it is missing from task manager, system tray etc? 2) If you are sure that MM4 was closed, can you re-test to be sure that it is MM5 that closes the MM4 instance? 3) As you are indicating that this is a regression, can you test in which MM5 build this started ? 4) Is it related to all MM4 instances or only to the instance located in C:\MediaMonkey\ directory? 5) Do you have "MM as service" installed in MM4 or MM5 (Option > Media Sharing) ? |
|
|
1. yes no traces of MM4 task 2. Sent you offline screenshot where MM4 is in background and MM5 starts 3. I can test earlier builds, but usually I have both MM4 and MM5 started. For now I tested and there is no issue in 2532. EDIT: 2614 Also do not have issue. So I guess as both MM4 and MM5 crashes it is related to fixes in 0017654 0018944 and 0018989 4. Starting 2615 crashes all started instances of MM4 no matter if they are normal or portable 5. No. neither one are installed as service. NOTE: If MM5 as first started and then start MM4 then all works OK, this only happen when MM4 was started first and then Start MM5. Sent you Crash logs from Both MM4 and MM5 along with MM4 crash log window, that is hidden behind MM5 splash screen. |
|
|
As discussed offline, Michal can replicate the issue on current SVN sources, so assigned to him (to inspect this issue/regression). EDIT: According to Michal this isn't regression, but seems to happen on certain conditions, to be found what it is... |
|
|
I reproduced it even with the build from the sources from the last November. Analyzing, as I cannot reproduce it with clean 2615 with the same data, ini and settings. |
|
|
So I can reproduce it with any MM5 release from at least whole last year, but only if I run MM5 from EXE shortcut (from desktop or windows taskbar) and in case MM4 window is not minimized. When running by double-clicking EXE, I cannot reproduce at all... Edit: so the last version working even with shortcuts is 5.0.0.2338. All following versions, starting from 5.0.1.2400, are affected. I.e. after leaving Chromium 79 and using Chromium >=90. |
|
|
It's somehow related to new chromium as current sources with chromium 79 work just fine |
|
|
It seems that newer Chromium sends a mouse event message on MM5 start that crashes MM4. The solution could be either to fix this crash in MM4 and re-release MM4 or (better) find which message it is and supress it in MM5 mouse hooking (or related Chromium code) -- as the issue does not exists with MM5 mouse hook uninstalled. Assigned to Michal to do further testing per IM instructions (related to the mouse hook message that crashes MM4). |
|
|
Fixed by changing message ID for MM5 |
|
|
Verified 2617 |
