Quote:
Originally Posted by robko
I'd have been just as happy if it reset itself because I don't keep a paperclip handy.
|
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.