-
-
Notifications
You must be signed in to change notification settings - Fork 1.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
consistent crash on file load #4928
Comments
Yep, it is. |
Ah, this is the background to #4929. I'm surprised MuPDF takes down the whole program here. |
How did you manage to save the last opened document if it crashed, btw? |
I simply pressed "open next file" at the end of a file, from a previous file in the same folder. |
But that's not how it works. If I open a file and crash the program, the in memory settings crash with it. Something like the last opened document will be lost. Generally speaking I consider this a bug, not a feature, but those settings will only be saved in case of a clean exit. Never in between. Settings pertaining to a specific document will be saved when exiting the document. This too is a bug, for which I've prepared a solution but I haven't wanted to tackle migration. If you purposefully edit the last file pointer to a broken file or break the file afterward, you'll see this on startup: On closer inspection of your log, the program does not actually crash. It seems to quit when it should be showing you the file browser. Do you have any special settings?
|
Oh, never mind. There's a code path that leads to a proper exit, possibly to prevent memory corruption? That's what'll cause it to save the last opened file. koreader/frontend/apps/reader/readerui.lua Lines 465 to 484 in 717db55
It can be easily triggered by this CBZ test file. It's a random source code file renamed I've never encountered this code path before, in the past five years. ;-) |
Issue
consistent crash on file load ( the file is possibly corrupted )
crash.log
(if applicable)crash.log
The text was updated successfully, but these errors were encountered: