99% work is using the Linux version. Crashes lately are frequent when tagging. My workspaces typically have 1-2 projects and 100k-150k files. The other day it took 5-6 tries restarting vs to get the tag file to finish. This wasn't typical 6 months ago...not sure what changed. But those crashes are generally not a huge problem for config/buffers saving because I just start vs and let it build the tag file. If it crashes, the worst is just that if I don't notice it to restart vs, it may take a long time to eventually get the tags built.
My issue with configuration is more with concurrent instances of vs. I want them all to have the same configuration, and if I change a setting, I want it to apply to all of them. What I'd really like is a single cloud configuration DB and all instances (home, work, Linux, Windows..) constantly stay up-to-date with that version. If I find the need to change a setting, I shutdown all instances of vs (typically, I have 3-5 open) but one, make the setting change, shutdown the last instance (I could do "save-config"), and then start them all back again. I've been doing that for years, swear it sucks every time I do it, and just move on. So I really want don't want multiple configuration folders.
General crashes are somewhat random, and really not that frequent. Infrequent enough where I don't bother saving my config/buffer state often, so when they do happen, I typically lose my recent browsing/work history (w/regards to files I was browsing). Since this is infrequent, I'd say it is much more of an annoyance than a problem; however, auto-saving the current file list just seems like such an easy thing to do, when it happens I'm always baffled why I have to run into this problem at all.