Using keyboard shortcut to "Save As" Causes Immediate Crash of VS
-
@Boldline I tried on MacMini M1 (with version 1.0.062) and could not replicate this issue.
Is it crashing if the Save or Save As is selected from the menu? -
@vectoradmin I just tried it again to be sure - this video shows me attempting to save the file (after I do the workaround for the other M1 issue of typing out some text and closing the file each time I open VS fresh)
I tried using the save and save as options from the file menu in the video and neither worked - both times it crashed and then the third time I tried a keyboard shortcut command-s to save and that also crashed it like the others
I'm also not getting any automatic crash report popups to fill in to send. I don't know if that's a factor. I upgraded to Monterey last night, but then used VS today with no issue - saving and everything. I'm not sure why now it stopped working and started crashing.
Is there a file I can send that would help? Or a way to get the crash report pop up to show up again?
-
@Boldline MacOS places the crash logs in ~/Library/Logs/DiagnosticReports/
If a crash was caused by VS, the crash log has VectorStyler in the file name.
It looks like in this case the crash happens somewhere else, but of course it is affecting VS.What was the last folder you saved (or opened) a file with VS?
-
@vectoradmin One thing to try: some VectorStyler data is saved by MacOS in ~/Library/Saved Application State/com.vectorstyler.savedState folder.
Exit VS and delete this folder (it is mostly window positions, Open/Save dialog state, etc).
Then try Save As again. -
@vectoradmin
“What was the last folder you saved (or opened) a file with VS?“Can you rephrase this? I’m trying to follow what you’re asking - thanks!
-
@Boldline After updating to Monterey, did you manage at all to save a file with VS?
and if so, does that folder still exist? -
Just to say I've no problems here using Shift-Command-S or Command-S (Save or Save-As) and v1.0.062.
I have noticed though that Command-S doesn't reset the saved icon colour, ie it stays red.
-
@vectoradmin said in Using keyboard shortcut to "Save As" Causes Immediate Crash of VS:
After updating to Monterey, did you manage at all to save a file with VS?
and if so, does that folder still exist?Yes I was able to do work in VS and save it properly in VS AFTER upgrading to Monterey. In fact, the file I sent you yesterday by email (screenshot below) was done completely in Monterey/VS and saved just fine.
I was able to reopen that file today without an issue. I tried to save it today and VS closed immediately
-
@Boldline I will try to find a fix for this issue, and add it to the next build (should be out Monday).
-
@Ingolf You're using an M1 mini with 16gb ram and running Monterey just as I am, correct?. Are you not having any issues with save and save as and export? (causing VS to quit suddenly)
-
@Boldline said in Using keyboard shortcut to "Save As" Causes Immediate Crash of VS:
@Ingolf You're using an M1 mini with 16gb ram and running Monterey just as I am, correct?. Are you not having any issues with save and save as and export? (causing VS to quit suddenly)
Correct. No, I tried immidiately I saw the posts here, but no crash on save, save as or export.
Does it happen with a new document based on defaults too?
-
@Ingolf Yeah it seems to happen whether its a new file or an old file. I sent @vectoradmin my crash report and he 's on the case. Seems like it's something that broke when I upgraded to Monterey. Still odd that it's not affecting you (I'm glad). Hopefully the developer can get a swift fix done for the next build!
-
@Boldline said in Using keyboard shortcut to "Save As" Causes Immediate Crash of VS:
@Ingolf Yeah it seems to happen whether its a new file or an old file. I sent @vectoradmin my crash report and he 's on the case. Seems like it's something that broke when I upgraded to Monterey. Still odd that it's not affecting you (I'm glad). Hopefully the developer can get a swift fix done for the next build!
This mini was never upgraded - came with Monterey from factory.
-
@Ingolf That's interesting. Mine came with Big Sur preinstalled. I wonder if that plays a role
-
Don't know if this helps but my Mini (16gb) also updated to Monterey from (factory installed) Big Sur.
-
@Jono @Ingolf Did either of you purchase your copy of VS from the Apple Store?
Yesterday @vectoradmin and I had narrowed down the issue with the save/save-as crash to only occurring in the standalone release version of VS, when I installed a version from the Mac App Store, the save/save-as worked as expected🍎 macOS Tahoe 26.2, Mac mini (M1, 2020), Chip Apple M1, Memory 16 GB
Cintiq 27QHD Display and LG Ultra HD Display -
-
@Boldline So far it looks like the VS cannot open the save panel, in the regular (notarized) version, but it can do so in the sandboxed version.
One explanation for this (and the inability to replicate on other systems) could be that some "state" of the save panel was stored, and that "state" causes the crash.
It is important to know that MacOS stores the state of Open and Save panels and this state is uniquely associated with the application.
But if the app is sandboxed, than it will receive a different "state" for the Open / Save panels.What "state" this could be, and if this the reason for the crash is unknown at this time.
It could be that some plugged in media was selected last time in the Save panel, but could be something else entirely. -
@vectoradmin hmmm ok. Well, I do know that I have been using a usb thumb drive attached by a usb hub to my M1 mac to store files on. I also have my intel machine nearby that I connected file sharing to via an internet connection. (One computer gives me an IP address to type into the browser of the other computer and I can attach a drive from the other machine drop files into, save files to and open files in.
At different times, I've had that connected and disconnected as I figure things out - could that have messed up the save and open panels? -
@Boldline said in Using keyboard shortcut to "Save As" Causes Immediate Crash of VS:
At different times, I've had that connected and disconnected as I figure things out - could that have messed up the save and open panels?
It is only a speculation, but I think it is worth trying out if some other than the default file system was mounted and visible in the Save panel, when it was closed last time.
If there are not too many possibilities, that I think you should try them out (USB drivers and network).
