Quote:
Originally Posted by ownedbycats
On the bugged versions, I was able to rarely trigger it by re-connecting immediately after importing new books, which made me suspect either the import process or cover generation. But I think DNSB or someone else said that the sql-wal files didn't show up for those processes so I'm not sure.
|
Even if cover generation doesn't leave the database open, you could still get filesystem corruption that messed with the database. That would be much much harder, however. But that could explain why it is hard to reproduce too.
Does calibre
always send a cover, or just when it has one?
Also, I'm not saying cover generation specifically causes it, I'm just saying things
like that might.