This was in the 3.16.0 thread, but it and the reply belongs here.
Quote:
Originally Posted by frostschutz
Did it really hang? Or did it reboot just in case? With forced reboots, you never know.
Right now I have a reproducible reboot: Browsing a collection with 47 books in it, and the books did not have their thumbnails created yet, causes sickel to reboot.
After killing/stopping sickel, I can browse the collection. It takes a bit longer to flip the page and you can watch the cover thumbnails being created, but it works.
Now, in my case my collections were created programmatically. Maybe the problem would not exist if you created them the normal way (book thumbnails would unlikely to be missing then).
But I still think it's a valid example that such a watchdog system is a double edged blade: In this case it caused a problem, rather than solve one.
It could display a confirmation dialog instead, what browsers do when JavaScript seems to be stuck in an endless loop. Just because nickel died doesn't mean the screen won't work anymore. It could tell you about pinhole reset method the same way. And it could be less aggressive, 5 seconds is not much.
It's complaining on a high level for sure, lets wait and see if other users have issues with it or not.
|
When I tried this yesterday, I couldn't reproduce it. But, I started the setup to get closer to what I think you are doing. Then I started having a reboot that I blamed on something else I was testing. This morning I realised the reboot was probably sickel doing its thing but the other testing I was doing was causing the hang. I also decided to test the collection because part of the other testing meant the library lists were showing as cover only lists. And yes, the collection I created yesterday with about 200 books caused the restart. But, a similar one on the Aura HD didn't.
Looking at it, it isn't the size of collection but the particular books displayed. It just happened that the first page of the collection I was using on the Glo HD had some larger books on it including some PDFs. When I sorted the working collection on the Aura H2O by file type and paged back from first page to the last, it hung and then restarted.
And this isn't just the collections, it is the main library list as well. The reboot I was getting was because the main library list was using the cover view and it had a couple of PDFs that didn't have a cover generated for them. When I managed to get back to the list view, it didn't reboot until I went to page two. And turning off the cover display stopped it completely.
So, there is a problem with the auto rebooting. It is probably on the tuning side of things or making it a bit more aware of what nickel is doing and allowing more time. Prompting to wait or restart like Windows does would be good, but I can see a problem with that. As nickel is the user interface, any attempt to get it to prompt the user would fail. That would mean interface function would need to be added elsewhere that showed over nickel. Probably not hard, but it does raise the complexity of this.