Quote:
Originally Posted by rashkae
(or a mix.)
|
I have a mixture of both. My Library contains around 40 books whith 2/3 of it downloaded from Amazon. Though I really doubt that this is Calibres fault and I would like to explain this:
The Kindle underlaying system is Linux if I recall correctly. The Kernel differs between Userland and Kernel processes. If a Userland application crashes (by any means) then this should never ever cause a full system crash (including reboot).
Therefore the issue might be related elsewhere and could be anything. Starting from experimental gcc compiler flags (or maybe they use clang). The Kernel as well as libraries (like libpng or some xlib libraries) could be compiled and generate badly optimized code (cpu mnemonic) and so on. Of course it could also be Kindle's proprietary Startpage and Booklauncher. Though even if this has issues, it shouldn't cause the Kernel to completely reboot or reset.
Anyways I don't know much about how the Kindle stuff really works, therefore I am more speculating here.
The explaination about "big" covers might make sense. Amazon usually has 300x500 pixels or something. And if you use covers with bigger sizes then it might cause crashes because the covers must be load into memory. And if there is not enough ram... Well then it might crash.
But then. All books sideloaded with Calibre (on my system) has covers from amazon only! so the covers should match the requirements.
But! if you have 500 books and eveyone of them is thumbnailed on Kindle launch (e.g. all covers loaded) then you might end up with this. Example!
300x500x32 (300 pixel width, 500 pixel height, 32bit png)
= 4.8mb per cover
If you have 500 books and all of them load on the go (rather than on demand) then you might end up with this:
500 x 4.8mb = 2.4gb of ram
That's theoretically now. If you go into the thumbnails folder of your Kindle, then you usually end up seeing gray-scaled png or jpg files. Maybe 16 colors ? (8 bit). This could be calculated like this:
300x500x8 = 1.2mb per cover
500 x 1.2mb = 600mb of ram
In case the covers are loaded on demand (e.g. loaded when swiping) and removed once the next page got loaded. Then it may be that the covers are not memory free'd correctly. E.g. memory leaks.
Now if we continue:
I saw that the entire kindle shop seems to be based upon index.html page containing a shitload of javascript magic. It could be that the underlaying javascript engine - in case it's used the same way for the "grid books library" - may suffer from heavy memory leaks. This of course (if you swipe through a library full with 500 books) end up in a shitload of memory leaks - which causes the system to ... yea .... to crash!