Quote:
Originally Posted by davidfor
Can you point me to the definition of "normal usage"? Reading the type of PDF that causes sickel to kick in when generating the cover image is probably a fairly unusual action. It is for me. I have them on my device but only because someone here complained about something and I loaded some large and complicated files to see what happened.
|
Quote:
Originally Posted by davidfor
Sorry, but the average Kobo user probably doesn't care because they aren't seeing any reboots. Be honest Jon, how many times did you see the device reboot before you patched sickel out? Personally, the count is 2. And both times I did something deliberately to see if it would reboot. Both times I chose to look at books that are on my devices purely to debug problems reported on this site. So, my normal usage will not trigger a wrong sickel reboot. My son's usage will not trigger a wrong sickel reboot. My wife's usage will not trigger a wrong sickel reboot. My mother-in-laws usage will not trigger a wrong sickel reboot. My belief is that not very many users will trigger a wrong sickel reboot.
At the moment, I can trigger this in two ways: going to a library list showing covers when one specific PDF is on the list and opening that PDF. That's one out of the 15 or so PDFs on the device.
GeoffR has a restart by opening the reading stats immediately after rebooting. I can't reproduce this. My guess it is related to the size of the database. Specifically, the number of books and the number of rows in the Events table. You would also get a restart if you had the bad luck that the last book being read was one that triggered the restart when the cover was generated.
Someone mentioned a problem with creating a bookmark. But, I'm not sure if this was with 3.17.0, or 3.16.10. I have made at least 50 annotations since I had 3.17.0 on my devices and haven't had a problem.
If there is another way to consistently get a restart with 3.17.0, I missed it. Please point it out so I can see if I can reproduce it.
Now, do I think Kobo got this right? No. I can see the point of what they are doing, but I'm not convinced it is a good idea. And they have something wrong with either the timing or when it gets involved. Hopefully Kobo will solve the problems quickly.
|
I'm re-reading your posts for my 100th time and I just cannot understand how the hell you defend Kobo. And I am specially astonished because you are a coder yourself...
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. So if you just have one file like this one,
BANG!!!!, you are dead. You won't be able to browse your Library because each time you reach the page containing that file the device will restart...
So Davidfor, you are wrong. Your son will probably trigger it if he has scanned comics or fanzines in his device...
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...
Davidfor, NTFS is supposed to support files up to 16TB (approximately). Would you defend Microsoft if one system choked with a 100GB file because that kind of files are not "common"? Or would you defend them if they choked with file names containing "ñ" when they are supposed to support Unicode?
And I don't give a damn if less than 1% people read scanned comics, Kobo say they support pdfs, so therefore DO IT!!!
WTH! I myself build some computation Excel spreadsheets (with VBA macros in some cases) in my work... And I had NEVER EVER suffered an issue remotely similar to this one and you can imagine which is my Q&A team...
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).