using the latest 70.0.116.13712 and same as before: opening files halts pico wokring and crashes Finder as well - I have to restart my mac, which I never do ever
my other issue with entering vehicle detailes crashing pico is also still present
Sorry to hear there are still issues on MAC. Does the stable build work OK? 7.0.109? Which flavour of MAC are you using? Monterey, Ventura, Big Sur?
We've not seen any support tickets for Mac crashing which would make me think you are reporting via the crash reporter. In case something has happened with the crash reporter, can I ask you to send in via support@picotech.com please. This will ensure any issues get in front of the support team.
Thanks again for the information as it all helps to build the picture.
I've been asked by the software team if they could have the files you are attempting to open which results in the finder stopping as they haven't been able to replicate the problem you are seeing.
There is a slight issue with the attachments on the forum at the moment which the web team are looking into. Could I ask you send in via support@picotech.com and put my name on the email so it will come through to me.
They're also asking if there is a trace file you could send on as well. This is a session file that is stored when the software closes.
Open a terminal window and change to the .local/share/Pico Technology folder
- the file itself didn't matter
- the drive was a read-only one where the file is kept and already opened once
- I'm trying to open it again from the list in pico, when the anomaly happens
If we can have a file from your PC then this keeps things the same, as much as we can, when trying to replicate the issue.
I've been provide with an additional way to find the trace file.
1. In Finder, from the top menu click Go > Home
2. Press Command-Shift-. to show hidden files (if they haven’t already done previously)
3. If they then click the greyed out “.local” folder
4. Click “share” then “Pico Technology”
5. Open the folder that has loads of letters and numbers and begins with “a”
6. There should hopefully be a “Report_yyyy_mm_dd.zip” file or trace.xml file they can send (note that the trace.xml needs to be sent immediately after the crash or it will overwrite with fresh data on next successful launch)
Let me know when you've had a chance to send it through and I'll look out for it on the support desk tickets.