The BrightScript Crash Logs table in the Developer Dashboardโs Channel Health report now provides access to complete stack backtraces.ย This enables developers to identifyย which file and line of code caused a crash and analyze the sequence of calls that led to it.ย The backtrace is available for both public and beta channels.
Developers can sort the crash log to find the most common recurring crash, and then open the backtrace to determine exactly where the channel application is failing for that crash. This helps developers efficiently triage and resolve crashes in order to improve the channelโs user experience and performance.
To access the stack backtrace for a channel crash, follow these steps:
- In theย Developer Dashboard, clickย My Channelsย in the left-hand navigation, and then clickย View Analyticsย for the channel.
- In theย Channel Healthย Report, scroll down to theย BrightScriptย Crash Logsย table.
- Click the link in theย Backtraceย column of the crash you want to investigate.ย
- The backtrace report lists the date, Roku OS version, channel application version, and stack backtrace report for each instance of the crash. ย This report list a maximum of 1,500 stack backtraces.ย
Theย BrightScript Crash Logs table provides a maximum 7 days of dataโregardless of the interval or date range selected in theย Filtersย section at the top of the report page.ย If the specified filter exceeds 7 days, only data for the last 7 days of the period are provided (for example, if the specified filter is from January 1st to January 31st, data is only returned for January 25โ31.ย
For more information on using the stack backtrace in the crash log, see theย developer documentation.
Read the Full Article on the official Roku Blog
