Frequent crashes

[ajkessel]

Device

Kobo

KOReader version

commit a8c0725

Model and firmware version

Kobo Libra 2

Issue description

I've been getting frequent crashes since installing the latest code from git. Does this log have the info you need to identify the cause(s)? I've redacted the URLs so I don't think there is anything private in here.

crash.log

Steps to reproduce

1. Go to '...'
2. Click on '...'
3. Scroll down to '...'
4. See error

Log

Additional information

No response

[quicklywilliam]

Hmm, I see the crashes but it's not clear what is going on. The crash is in ReaderFooter – not our code, but that doesn't mean it isn't our fault. It looks like the file is an old version of ReaderFooter as well, guessing this was in the last KOReader release?

Do you have any steps that can reproduce the crash?

[ajkessel]

Hmm, I see the crashes but it's not clear what is going on. The crash is in ReaderFooter – not our code, but that doesn't mean it isn't our fault. It looks like the file is an old version of ReaderFooter as well, guessing this was in the last KOReader release?

I'm just using KOReader 2025.04 Full Moon. When you say "old version", do you mean I might have the wrong version of KOReader or some part of it?

Do you have any steps that can reproduce the crash?

Just opening articles, trying to change fonts, almost any action. Happens frequently without any consistent cause. Until I updated to the latest ereader code, though, I was not getting crashes commonly.

Is there something I should do to try to have a "cleaner" install? If you're not seeing frequent crashes on the latest code, there must be something odd in my setup.

[ajkessel]

Just to clarify: I should be using the latest official release of KOReader, not a build from the latest git commit, right?

[quicklywilliam]

Yep! Though I've tested both and I haven't been able to reproduce this crash on either…

[ajkessel]

I still get it frequently. Anything I can do to provide more useful debugging?

[quicklywilliam]

Aha, I was able to reproduce it! After looking at the crash log again, I saw this bit:
07/19/25-23:53:57 INFO opening file ./settings/ereader/instapaper/1858481361.html
07/19/25-23:53:58 INFO Inhibiting user input
07/19/25-23:53:58 INFO opening file ./settings/ereader/instapaper/1858481361.html

This was right before the crash - looks like you were somehow opening the same file twice in rapid succession. Any idea how that might be happening?

On my setup, I was able to reproduce this by rapidly tapping different undownloaded articles. I suspect this is a regression due to the new background downloading work (a2d7486).

[ajkessel]

It's possible I've tapped twice on one article or two different articles. It's not clear when an action was received and something is in progress vs the tap wasn't actually received (for example because the finger was slightly outside the relevant tap zone).