Crash in MacOSX

[BenDevPlusPlus]

Hi, this is the husband of the Reddit user LittleBeyond who loves this app and is begging me to figure out why it is crashing on her. I have two crash reports I will paste in here.
Describe the bug
App is launched, stays open for a few seconds to a minute, even successfully downloading a book from an account. But without any user action, the app crashes and disappears or hangs and will not respond. This only occurs when the end user's original LibationContext.db file is present in the Libation settings folder. Unfortunately, it contains all the data of the 3000 audiobooks currently being managed with this app, so replacing it is a last resort.

Platform

MacOS 14.5
Hardware: 8GB ram, 1TB SSD Drive with 160GB free

Log Files
There are two logg I have found. I will attach them. Here are links too in case Github doesn't actually attach the files:
https://drive.google.com/file/d/1MiBZy_vPo1Ji57twoyUuXMNugUXont7E/view?usp=sharing
https://drive.google.com/file/d/15okpFYJwm8jMpq2iyaVpfBRo6jin8kXT/view?usp=sharing

Libation Crash Log 2.txt
Libation Crash Log 1.txt

. They are huge because it lists the state of every thread unfortunately.

I do have the LibationContext.db file too let me know if that would help to debug. Thanks!

[BenDevPlusPlus]

Oh here is the log zip file too which generated after I reinstalled to try to get things working. I moved settings files and db in and out to try and figure out where the problem was but didn't really get anywhere besides the db file seemingly being related to the problem.

_Log202502.zip

[rmcrackan]

Hello, husband :)

Thank you for the logs. tbh I don't know how to glean useful info from the mac ones but the Libation one was very helpful.

One thing to try is using the latest pre-release. Although v11.1 is the latest official release and has been stable for nearly all users, there have been improvements over the past year that I just haven't officially released yet. I actually intend to do a release very soon but my job has been ... not wonderful lately ... so we'll see.

Lemme do a quick primer on Libation anatomy for context: you add your account/s (this info lives only in AccountSettings, not in the database), you do a scan during which Libation imports your audible library into the database, and you do the liberate/download step during which it downloads your decrypted audiobooks. During the liberate/download step, it also updates the database with info about whether downloading was successful. If you manually put tags on books, this also lives in the database.

All that to say: if you've had no successful downloads, then you can actually delete a problematic database file and start over. (Well, assuming you have the account access to do a new scan.) Even if you have downloaded books, I can tell you how to account for these; my reply is already going to get plenty long though without adding yet more details. We can talk about that later if needed.

Mac can act differently than the other operating systems so I made this page about it. I highly recommend going through it when there are mac-specific issues.

The final logs before a new session are telling. ie: the last thing logged before your crashes.

• A lot of them seem to be during a scan. Let's turn off auto-scan (in the 'import' menu) so you can better control and monitor scans. This would also explain why it happens when unattended: because something is going wrong during a scan and the scan periodically takes place on its own if auto-scan is on.
• A few times, the probable crash is during a download and the last thing logged is something like the window size changing. Is there something fighting for control over that file? I've got all my stuff on dropbox and sometimes when I'm running Libation, dropbox seems to be trying to aggressively read files and Libation is in the middle of creating or editing. I could imagine this being true for anti-virus or icloud/dropbox/gdrive/onedrive/etc
• You're trying to split books by chapter. This is a fine choice, but for purposes of debugging, could you see if it makes a difference to not to so. No -- I have no idea why this could be a problem. I'm just brainstorming.

Oh yeah, the logs. This is odd -- the only errors of substance that I see are 'license denied' errors. Those won't cause a crash though. Let's get you up and running though then we can address these.

I know I dumped a lot on you. I recommend starting with the mac page and the pre-release upgrade and going from there.