Quote:
Originally Posted by arspr
The pdf file that 3.17. cannot manage because its thumbnail generation causes a reboot is just a 29 Mb one...
And this failure happens 100% of the time.
AFAIK, Kobo says that they support pdfs. So they MUST support EVERY kind of pdfs. I don't care if they are a collection of photos, OCR text, AutoCAD digitalized graphics or whatever. Specially when we are not talking about torture-test pdfs...
This is not a 1GB pdf file or something like that, (and this is not any of the two issues described in the pdf performace thread). It's a damn less than 30 MB file which only has one particularity: it's just a collection of images with no text...
And I don't give a damn if less than 1% people read scanned comics, Kobo say they support pdfs, so therefore DO IT!!!
More over I cannot defend Kobo in any way when the solution is as easy as increasing the threshold time...
And please, Davidfor, test the Upgrade Dictionary process I've also posted because I am 95% sure that you get a reboot after it. (I cannot test it anymore because I've patched my 3.17 installation). |
So far on my updated H2O (3.17.0 no sickle patches), I have had zero restarts from sickle. Not one.
I have downloaded various dictionaries - no restart (Reported by a handful of users as a 100% cause for sickle to trigger)
I have checked the rewards - no reboot (Reported by Geoff as 100% trigger)
I haven't tried loading a PDF because I generally dislike them. However consider that the PDF you're talking about is several times larger than the average ebook, and contains images which generally ereaders pause over.
And no, if your usage is that of 1% of the usage of those using Kobo's you really can not expect the company to code around your usage. It just wont happen.
Should Kobo extend the timeout? Probably. Is it anywhere near the 'omg the sky is falling and it's all Kobo's fault' situation you're trying to make it? Nope. The typical user, those 99% folks, will not see this issue. They wont care if sickle is there because for them it's effectively not there.