[Room Navigator] Persistent web app crash

[Benjamin R]

Hello,
I’m trying to integrate the URL of our digital signage application via the "persistent web app" feature.
However, I’m experiencing frequent crashes when loading the URL.
After checking the crash files from the player’s interface, I noticed that the errors seem related to the available memory size.
Our application uses around 150 to 200 MB of RAM.

Is the player able to handle this memory load, or is there a known limit that should not be exceeded?

Player: Cisco Room Navigator - Model TTC5-15
URL used: https://display-v2.testing.dynamicscreen.xyz/golem/?model=cisco

Crash report from ‘crash-metainfo’:

-- GUI error report start --
GUI error tag WebEngineTerminatedError
Tue Aug 12 12:13:55 2025
GuiError: Render process exited with signal 9, exit status 0, webview type PersistentWebApp, status crashed, profile: persistent, pid: 3414, killed by webmem watcher: false, javascript heap memory usage: 153169963, memory increasing recently: true
-- GUI error report end --/bin/acr-reporter-gui

Crash report from ‘crash-counter.log’

Tue Aug 12 09:53:03 CEST 2025, exec: /bin/kernel-log-tracker, command: /bin/kernel-log-tracker-cgroup-oom
Tue Aug 12 09:53:09 CEST 2025, exec: /bin/acr-reporter, command: /bin/acr-reporter-gui

[Benjamin R]

Thanks for your reply, sorry about the delay I had a few days off. 
We have indeed a Room Navigator with 4GB of RAM. We also identify a pattern when the crashes occurs:
If we load our application without any code calling xAPI, the player runs without any crash.
However, crash happens when we try to use xAPI. We tried some scenarios:
- default behaviour: our application loads, at one point it will use the dedicated Cisco javascript class using xAPI to request the serial number. A few seconds after it crashs.
- delay xAPI call: we also tried to wait for our app to finish loading, 15-20sec later we call xAPI, the player either crash or hard freeze: not responsive, restarting it from admin can take up to 5min (the led is off, but the screen is still in a freeze state)
- call xAPI from the chrome inspector: we load our app without xAPI calls, then call getXAPI() from the chrome inspector, we noticed the player being slower while getXAPI returns its value

[Benjamin R]

After looking at the page, yes we are using a 4GB of RAM device.

Our application uses mostly javascript and runs well on a device that has 4GB of RAM. Do you know if this kind of player has a dedicated memory space for javascript? Maybe there is a limit that the app reaches and causes the crash.

[Jonathan Schulenberg]

The only public documentation I have seen on this is the RoomOS WebEngine Developer Guide which has a performance section but it's really vague. The Developing web applications on the Room Navigator doesn't cover this either.

Have you been able to identify a pattern to the crashes (e.g. when a specific media element plays or after X amount of time)? And does simplifying the page layout/elements reduce the crash frequency?

I'll ask a few folks but you may want to pop into the Ask xAPI space as well. 

Earlier Room Navigator units shipped with 2GB of RAM. This was later bumped to 4GB to better support MTR. Presumably that additional RAM raises the ceiling for the web engine as well though. Check the PID that you're testing with.