Roku Developer Program

[RokuJoel]

"ljunkie" wrote:
FWIW, I usually hit ctrc-c once the channel starts loading to verify it won't crash while I want to debug something, or if I have an implicit stop in the code. I'm guessing most have seen the pattern, but it will crash the debugger every other time.

This has been an issue since the release of the Roku2 XS, and it made its way backwards to the 3.1 firmware platform as well. A bug has been filed. Note that this is a different issue - the issue that was being discussed in this thread, if I'm not mistaken, is an actual crash of the Brightscript environment itself and the resulting reboot of the device.

- Joel

[ljunkie]

Yep, didn't mean to hijack as it's not the exact same issue, but I figured I'd put in my two cents in case anyone came to this thread. Thanks for letting us know there is a bug report, it's second nature now so I'll probably keep doing it even if fixed 🙂

"RokuJoel" wrote:

"ljunkie" wrote:
FWIW, I usually hit ctrc-c once the channel starts loading to verify it won't crash while I want to debug something, or if I have an implicit stop in the code. I'm guessing most have seen the pattern, but it will crash the debugger every other time.

This has been an issue since the release of the Roku2 XS, and it made its way backwards to the 3.1 firmware platform as well. A bug has been filed. Note that this is a different issue - the issue that was being discussed in this thread, if I'm not mistaken, is an actual crash of the Brightscript environment itself and the resulting reboot of the device.

- Joel