>>13181
Thanks, I will keep thinking about this.
>>13187
Hmm, that is odd. When it crashes, does it throw up any error window at all, or just close itself? Does the close look 'clean', or does it just die in one frame?
My first guess is the disconnection caught the db while a transaction was flushing to disk and so there is some bad data in there, although
usually that stuff is recovered from.
If you go to /Volumes/Drive/hydurs/db and check your latest client.log file and scroll to the bottom, is there any traceback error there for what happens after the 'booting db' phrase? A db error generally shouldn't cause a crash, so it is also odd that you aren't getting an UI popup of some sort saying 'hey, the db had a problem on boot'. If it is erroring silently and quitting the program neatly, there could be some error in there, but if it is a full-on actual crash, there won't be any kind of tidy-up statements.
If there is no error, let's check your db files. Here's a help file that is a slight pain in the neck to get to as an OS X user:
https://github.com/hydrusnetwork/hydrus/blob/master/db/help%20my%20db%20is%20broke.txt
It will walk you through some integrity checks to make sure your db is all ok. I think there is an OS X sqlite3 executable in your App, if you know how to navigate that, or you can get the tools here:
https://sqlite.org/2019/sqlite-tools-osx-x86-3290000.zip
Message too long. Click
here
to view full text.