Curious.... I'm starting to question the quality of the internal memory chip. I wonder if they are having premature failures? This might explain why hubs are just going dead without any (known to us) cause???
Mine choked for the first time today as well. I have noooo idea what it was doing but it took 30 minutes to get to the settings page to perform a 'graceful' reboot. It all started around 0500AM EST. No devices were responding. I had a few zigbee devices dropoff overnight as well, including my Pearl which SUCKED! WAS SCAAAARY!!! It has been OK since then...KNOCK ON WOOD!
At least you were able to boot back up. So the next step if it happens again is to see what app may be hogging the CPU. Sometimes I have my logs on overnight on my computer. That helps me see what may have happened and at what time.
I've had some corrupted rules in RM that caused issues (recently with Hub Link) - not that serious of course. Usually it's because I change the rule conditions and forget to remove/replace the related rule definition. It can be a little picky...
Again, we need better monitoring tools. Just think how many support tickets would be prevented if developers had the ability to properly troubleshoot their own running apps. Common sense if you ask me.