Started by ksm1701, September 29, 2020, 03:22:24 AM
0 Members and 1 Guest are viewing this topic.
QuoteWe investigated the crash report.When clicking the magnifying glass, PitStop starts looking for the document that matches the report.First it checks all open documents. This doesn't return a result, probably because:a timing issue causes Acrobat and/or PitStop to think the document is not open yet; or(more likely) the file path stored internally in the report doesn't match with the open document (perhaps because of how Fuji XMF works with files).Next it checks whether it can open a file at a path relative to the report.If nothing is found yet, it checks whether it can open a file at the path stored internally in the report. This is the same path as in step 1, but now it's being used to try to open a file rather than check whether the file is already open.As a final step we ask the user to point to where the file is. Evidently we never get to this step.So the crash is in steps 2 or 3. These two steps are indistinguishable in the crash log. Both these steps try to open a file at some path, and the crash log indicates that this fails. The crash log does not indicate why it fails, just that it does. One possibility is that Acrobat says this file is already open - although then it should have been found in step 1. Another possibility is a file system problem - e.g. no permissions on the path. These are just guesses at this point."permissions or access issue"I agree, this is a definite possibility. If in step 2 or 3 PitStop doesn't have read access on the path it's trying to open, this could indeed cause a crash. The two paths being checked are both stored inside the report; one is a relative path the other is absolute. I believe there recently was another support case where we showed how to find the path using Browser.My guess is that this different way of opening the document causes step 1 to succeed: the already open document is recognised as the correct one.However, the relevant code has not changed between PitStop Pro 2019 and 2020. On the one hand this means it's not something we broke, on the other it also means the problem is already present in 2019 (so downgrading just PitStop won't help).
QuoteThanks for investigating crash report and getting back to me.As there doesn't appear to be a clear solution or culprit to what is going wrong I guess I will just have to live with the issue.Out of interest, I attempted to re-install Acrobat Pro XI so that I could then try Pitstop 2019 with it to see if the issue still occurred with that setup but unfortunately the Acrobat installer didn't appear to install correctly.I have checked the install on a colleague's Mac and he is running the same version of XMF with Acrobat Pro XI and Pitstop 2018 and he doesn't have the same issue. He is, however, running Mac OS Mojave (10.14) whereas I and my colleague who is also affected are running Mac OS Catalina (10.15).Could that additional information shed any light on where the issue may lie?