2024-06-11, 06:21 PM
(This post was last modified: 2024-06-11, 06:31 PM by pcm. Edited 11 times in total.)
I kept having this *exactly same* issue too. I had (have) this issue on 1.9.2 and 1.9.3 (my current) and I had to change "Parallel library scan tasks limit" to 1 (it's 0 by default, which will set the number of scans to number of cpu-threads your computer can run).
And that fixed the issue for me because now there is only one thread doing the library scan and writing to library.db file and hence no way to do get into a race condition/deadlock ... Not the most performant solution but got the job done for me. Be aware that your scans will take a lot longer but they'll complete guaranteed.
You can find 'Parallel library scan tasks limit' config setting under "general" section in your admin-dashboard.
And that fixed the issue for me because now there is only one thread doing the library scan and writing to library.db file and hence no way to do get into a race condition/deadlock ... Not the most performant solution but got the job done for me. Be aware that your scans will take a lot longer but they'll complete guaranteed.
You can find 'Parallel library scan tasks limit' config setting under "general" section in your admin-dashboard.
