Forum Discussion

98thrxse's avatar
98thrxse
Binge Watcher
2 months ago
Solved

Unexpected app exit after a few hours

Hello Roku Community!
This issue started to occur on Roku OS 14.5. After 2 hours of streaming media, the app unexpectedly closes and goes to the home page. Automatic power saving and bandwidth saving are turned off, also the screensaver is disabled. The video starts every hour but video node is present all the time, which shouldn't cause a timeout. Additionally, attaching the logs before exit:

05-09 02:18:17.823 [beacon.signal] |AppLaunchComplete ---------> Pending Render Pass
05-09 02:18:17.891 [beacon.signal] |AppLaunchComplete ---------> Duration(1685 ms)
<Component: roAssociativeArray> =
{
    date: "2025-05-09T02:18:19Z"
}
<Component: roAssociativeArray> =
{
    date: "2025-05-09T02:18:19Z"
    mediaId: 288501
Component: roAssociativeArray> =
{
    date: "2025-05-09T02:18:42Z"
    mediaId: 288855
}
05-09 04:28:16.567 [beacon.signal] |AppExitInitiate -----------> TimeBase(7801392 ms)
05-09 04:28:16.647 [bs.ndk.proc.exit] plugin=dev pid=2944 status=exit retval=2 user requested=1 process name='SdkLauncher' exit code=EXIT_USER_NAV
05-09 04:28:16.726 [beacon.header] ___________________________

Additionaly, "disableScreenSaver" field is set to "true" for Video Node. What am I missing? Is there a way to prevent this from happening while playing video?

  • SOLUTION: In my case, the issue was that the video was too short (duration ≤ 1 second).

8 Replies

  • 98thrxse's avatar
    98thrxse
    Binge Watcher

    SOLUTION: In my case, the issue was that the video was too short (duration ≤ 1 second).

    • 98thrxse's avatar
      98thrxse
      Binge Watcher

      As far as I can see, until OS 14.5, a duration of ≤ 1 second was sufficient to prevent Roku from timing out.

  • 98thrxse's avatar
    98thrxse
    Binge Watcher

    An interesting fact is that AppExitInitiate is called before the video player state changes. I also checked if the buttons on the remote control are pressed, but no.

    06-25 16:08:46.341 [beacon.signal] |AppExitInitiate -----------> TimeBase(7201165 ms)
    onStateChanged
    buffering
    06-25 16:08:46.429 [bs.ndk.proc.exit] plugin=dev pid=13358 status=exit retval=2 user requested=1 process name='SdkLauncher' exit code=EXIT_USER_NAV
    06-25 16:08:46.498 [beacon.header] __________________________________________
    06-25 16:08:46.498 [beacon.report] |AppLaunchInitiate ---------> TimeBase(0 ms)
    06-25 16:08:46.498 [beacon.report] |AppSplashInitiate ---------> TimeBase(11 ms)
    06-25 16:08:46.498 [beacon.report] |AppSplashComplete ---------> Duration(952 ms)
    06-25 16:08:46.498 [beacon.report] |AppExitInitiate -----------> TimeBase(7201165 ms)
    06-25 16:08:46.498 [beacon.report] |AppExitComplete -----------> Duration(157 ms)
    06-25 16:08:46.498 [beacon.footer] __________________________________________




  • Tried to leave the remote without batteries, the problem is still there

  • I don't think this is an issue, because I tested app on different devices (Stick+ and Ultra), and it worked properly on 14.1.

  • renojim's avatar
    renojim
    Community Streaming Expert

    The thing that jumps out is "user requested=1".  Any chance it's something like a remote with a flaky button?  Have you tried it on multiple devices?