Quote:
Originally Posted by EastEriq
Motivated by this post, I had a new go on KOreader. I tried both the "stable" version mentioned there and the most recent 2020.8.1 from https://github.com/koreader/koreader/releases.
I have to say that coming from "just" cr3, I'm impressed. For one, Koreader is the only one handling correctly mixed LTR-RTL text, which not even the stock pbreader does.
However neither of the two versions I have tried holds. I've found uncountable ways for crashing the program, by turning just a few pages, by entering the settings menus, by sketching some gesture on the touchscreen (not even knowing what their effect should be - never got that far in the settings).
Unless that is really a feature for reminding me that no single book deserves more than a cursive attention to a couple of its pages, and to stay away from the vane and addicting illusion of fine-tuning the configuration, has someone had better experiences than mine? Is KR demanding too much from the resources of PB631?
If I log in with ssh, I for example see with top that the process
Code:
{reader.lua} ./luajit ./reader.lua
is taking 407Mb, 87% of VSZ on a particular medium sized epub, though I have still 157Mb free. Too much for headroom?
ETA: seen this thread, but it's old |
We did very promising improvements the last days (and by we I mean
ezdiy).
These changes affect all pocketbook devices and prevent some long-time wonky behaviour (like not repurposing the same instance when launched from PB library, that could explain the resources displayed on top)
Sadly, there's still one issue that doesn't happen on most devices but does(did?) happens on yours:
https://github.com/koreader/koreader/issues/6000
Short answer: try tomorrow nightly (or wait for the next stable). If you hit a SIGSEGV::SEGV_MAPERR error then I'm afraid you'll need to wait until somebody figures out what happens. If you don't hit that error there's a chance of everything working (mostly) fine
