I've seen it occasionally and suspect that there's a combination of things involved, but my guess is that there's some issue where certain books/pages result in the readers needing more memory than normal. If the reader's been in use for a while, that may not being available, due to it being used elsewhere in caches, etc, and the reader has a fatal error & resets. When it resets, the same book/pages can be read and, immediately after a clean start, the memory's available...
(There have been cases reported in the past where it's been possible to create ePub's which always crash the reader, but AIUI, those cases have been found & trapped.)
|