|
I did not yet have the time to check the logic with koreader. It's most certainly not a general failure, since the functionality has been tested. It must be some kind of corner case.
anton79ru: that might be a way for testing when/if corruption happens at all, but that route seems to be overkill. If the file is not opened for writing at all, it just cannot be the fault of KoReader. But mitigating failure conditions is the second step, the first would be to find out why they happen. A job for my weekend, maybe.
|