Libation crashes when book is at 96-99% downloaded.

[Willows227]

The last few days Libation has been hanging up at the end of each book download and then crashing the app. It seems the book has successfully downloaded into my library folder but when I reopen Libation the "stop light" is still showing red. If I try to manually mark it as downloaded that app also crashes.

It appears that I am able to do anything else within the app just fine (reorder, search, scan library, etc).

It originally began when using Libation Classic. I then tried Libation 11.1 and it still did it. Finally, I updated to the new 11.6.4.1 version with no change to the crashing issue.

To Reproduce
It happens at the end of any book download attempt.

Platform

Windows 11

Log Files

_Log202501_006.zip

Thanks in advance for any guidance you might have.

[rmcrackan]

Does this happen when your destination folder is on C: drive instead of P: ?

[Willows227]

Ok, I just tested it by setting it to the default location on my C: drive. It did the same thing.

_Log202501_006.zip

[rmcrackan]

Is there a more recent log file? The last entry in this one still shows P:\Audio Books

[Willows227]

Sorry it took so long to respond back... I went radical yesterday and deleted all the .json files to see what would happen. On opening Libation again, I let it scan the audible library and then had it locate previously downloaded books from my :P drive. That went slowly but successfully all night (but it is not done yet so I stopped it for now).

So, this morning I set the default download location back to the :C drive and tried to download a book.

Same thing happened... download status in Libation showed 98%, it froze and then crashed. Meanwhile, it appears the book was downloaded onto the :C drive successfully. On reopening Libation the book still shows a red light.

_Log202501_010.zip

[rmcrackan]

In the latest log, the download folder is always P-drive. There are a unrelated errors confusing me.

First: was the database manually altered? If not, there was a weird bug a while back which is causing lingering problems.

There are 4 books which have this database bug. My recommendation is to delete them in the Libation grid, go to Settings > Trash Bin and remove completely from Libation, then do a scan to have them re-imported, hopefully without errors this time:

• Battle at Avenger's Tower [B0CKKPR54C]
• Black Sands [1980052913]
• Brainwashing [1977388531]
• Dangerous Depths [1980053049]

The other bug is using the 'locate books'. Sometimes it finds the folder then can't actually read from the folder. Would you mind trying the same thing with Libation Classic? I wonder if this is about your computer, or whether it's a difference between Classic vs Chardonnay.

[Willows227]

So, after your last message, I tried to run Classic Libation and it caused a fatal computer error with a blue screen of death. After a fresh reboot, none of my Libation versions would load without crashing (which was a step back from earlier when it would load just not complete the downloads). I deleted ALL the Libation files (besides my stored library) and did a fresh download of the Classic version. Surprisingly, it loaded AND successfully downloaded all of my books in queue onto my :P drive! Yea!! I was hesitant to put anything on "auto", so I just clicked one book at a time as they downloaded. That was about 12 hours ago and everything has been running great. I ran the "locate books" overnight and it found some books but not nearly all of them. I can live with that though.

I have been using Libation all morning just fine and then.... for no discernable reason it froze and crashed again. It won't load at all and gives this Fatal error pre-log report:

The type initializer for 'LibationFileManager.AudibleFileStorage' threw an exception.

at LibationFileManager.AudibleFileStorage.get_BooksDirectory() in D:\a\Libation\Libation\Source\LibationFileManager\AudibleFileStorage.cs:line 43
at AppScaffolding.LibationScaffolding.logStartupState(Configuration config) in D:\a\Libation\Libation\Source\AppScaffolding\LibationScaffolding.cs:line 230
at AppScaffolding.LibationScaffolding.RunPostMigrationScaffolding(Variety variety, Configuration config) in D:\a\Libation\Libation\Source\AppScaffolding\LibationScaffolding.cs:line 103
at LibationWinForms.Program.Main() in D:\a\Libation\Libation\Source\LibationWinForms\Program.cs:line 67

Here is the latest log file I have...

_Log202501_011.zip

[rmcrackan]

There's an error for The system cannot open the file. : '\\?\P:\Audio Books\Series - YA - Grey Wolves'
Is this a valid path?

[Willows227]

Yes, this is a valid path.

I may have created my own nightmare by manually creating a filing system in my book storage folder.

I have created a system of subfolders:
Author - Henry, Marguerite

That contain stand-alone books and more subfolders for series:

• Justin Morgan Had a Horse [B002V1A1L4]
• King of the Wind [B00KQ19P54]
• Series - C - Misty of Chincoteague
  • Misty's Twilight [B00KIWUM7Q]
  • Sea Star [B002VA3978]

I further add in "C" for children's series and "YA" for young adult series.
I make no changes to each Libation-created book folder except for moving them into their designated subfolder.

I have a large book collection and this system works well for me. If Libation can't follow the book locations I can live with that. I would like it not to crash my program if possible. :)

Again, thanks for all the time you give to your users, it is appreciated greatly.

[rmcrackan]

Moving the files shouldn't be a problem. I haven't tested Libation with a library as big as yours. I can't imagine it would be a problem on a modern computer. It might be worth attempting to recreate your error and watch your computer's memory usage. There are a few errors which are impossible to capture such as running out of disk space on a log's drive or a program running out of memory.