问题
Obviously, after the crash Developer tools at port 9222 is of no use, because "Remote debugging has been terminated with reason: websocket_closed". How can I retrieve, for example, recorded timeline; or get call stack; or find anything about the reason the Chromecast decided to reboot itself? What are the best (or, for that matter, any) approach to debug Chromecast crashes?
回答1:
We need to look at your log file to see what is causing the crash. It is relatively easy to do that but we need some help from your side.
First, open the Chromecast setup app on, say, your Android device and go to the settings for your device. You should see a check box that states something like: "Send Chromecast usage data and crash reports to Google". If it is not checked, make sure you check it and then wait 15 minutes or so and reboot your chromecast.
Try to recreate issue and as soon as it crashes and reboots itself, open the setup app again and select "Submit feedback report" from the overflow menu. You will see a new window on your phone and make sure you enter the following text in the text box there "crash-vmt". We will be using this text to search among the reports that we receive to identify your log.
After doing that, please let us know (add a comment here) so we can grab the log for further investigation.
来源：https://stackoverflow.com/questions/22491574/is-there-a-way-to-analyze-chromecast-crashes