View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0019425 | MMW 5 | Other | public | 2022-10-04 12:56 | 2023-12-20 14:23 |
| Reporter | Ludek | Assigned To | |||
| Priority | urgent | Severity | minor | Reproducibility | always |
| Status | assigned | Resolution | open | ||
| Product Version | 5.0 | ||||
| Target Version | 5.1.1 | ||||
| Summary | 0019425: Conflict with Adobe Acrobat | ||||
| Description | 1) Download and install Adobe Acrobat Standard DC (64-bit) 2) Start Adobe Acrobat at first (it is important to start Acrobat before MM5 start) 3) Start MM5 4) Double-click PDF in Windows Explorer => PDF fails to open in Acrobat or it opens after a minute or so 5) Close MM5 => PDF is opened in Acrobat Note: The same issue happens even with Portable install | ||||
| Additional Information | [Ticket # 4780] | ||||
| Tags | No tags attached. | ||||
| Fixed in build | |||||
|
|
This issue is really curious, it happens also for portable version of MM5 and even if eveything about OS integration is unassociated/unregistered. BUT: It never happens when MM5 is started from desktop shortcut. i.e. starting from taskbar shortcut or Windows Explorer exhibits the issue, but starting from desktop shortcut never exhibits the issue. |
|
|
So far I haven't found what the cause could be, but my suspection is something inside Chromium because Acrobat DC is also using Chromium engine and for each PDF it runs new renderer process. - if MM5 is already running then there is no issue and Acrobat immediatelly launches new Chromium's renderer process for each PDF that is double-clicked in Windows explorer - if MM5 is started after the Acrobat then double-clicking PDF causes Acrobat's renderer process to start minute or so (or until MM5 is closed) - if MM5 is started via desktop shortcut then there is no issue for Acrobat to open the PDF immediatelly Reason unknown though.. |
|
|
Hmm, further testing shown that it's a bit more strange / complicated: 1) Run Acrobat 2) Run MM from desktop shortcut 3) Run explorer and double-click PDF in explorer => no issue 1) Run Acrobat 2) Run MM from taskbar 3) Run explorer and double-click PDF in explorer => freeze 1) Run Acrobat 2) Run Explorer 3) Run MM from desktop shortcut 4) Select a PDF in explorer and double-click => freeze 1) Run MM5 (no matter how) 2) Run Acrobat 3) Run explorer and double-click PDF in explorer => no issue 1) Run MM 2) Run Explorer 3) Run Acrobat 4) Select a PDF in explorer and double-click => no issue So whenever both Acrobat and Windows Explorer are run before MM5 then the freeze happens (no matter which way MM is started). Whenever Acrobat is started after MM the freeze never happens. When Acrobat is started before MM5 (but Windows Explorer is closed) then the freeze happens only when MM5 isn't started from Desktop shortcut |
|
|
This must be something deeper inside the Chromium engine, unfortunatelly recent Chromium update did not help here, assigned to our Chromium expert (Petr) .. |
|
|
Here's what I'm seeing (build 2819): 1 Run Acrobat (installed) 2 Run MMW (portable) via shortcut 3 Launch a PDF from Explorer --> Nothing happens! 4 Close MMW --> The PDF opens in Acrobat (so MM seems to somehow be associated with the pdf, but not opening it) 5 Open MMW 6 Launch another PDF from Explorer and wait 5 minutes --> System error: The code execution cannot proceed because HHA.dll was not found. Reinstalling the program may fix this problem. !! Could it be that MMW is, for some reason, trying to use PDFs as help files (HHA.dll is used to render help files)? |
|
|
Is it still relevant ? I've tried with current sources and work just fine. |
|
|
I just retested with build 2822 and the issue persists similarly to the description at 0019425:0073168 . 1 Run Acrobat (installed) 2 Launch a PDF from Explorer --> Nothing happens! 3 Close Acrobat 4 Run Acrobat (installed) 5 Run MMW (portable) via shortcut 6 Launch a PDF from Explorer --> Nothing happens! At this point 2 paths can be taken: A Original approach: Close MMW --> The PDF opens in Acrobat as soon as all MMW processes terminate (as observed in Task Manager) OR B Wait 2 minutes --> The PDF opens in Acrobat Note: I'm no longer seeing the system error described at 0019425:0073168, that could be replicated by performing a few additional steps. |
|
|
Can you confirm is it happening only in a first minute or so when MMW is running ? I've tried to wait ~2 minutes after MMW run and PDFs are opening immediatelly. |
|
|
Confirmed: if I run Acrobat, then run MMW, then wait 2m, then open a PDF in Acrobat via explorer --> it opens right away. So it would appear that MMW is doing something at startup that interferes with PDF's launching from explorer. |
