I have a web application running in a browser, on a balena-based RPI3.
From time to time, the screen shows the “Aw, Snap!” error from Chromium, which means that the browser tab process has crashed.
I have tried to look in the balena dashboard logs, but nothing about the crash is shown. I have also extracted the Xorg.0.log file from the container itself, but it also has no clues for me.
I suspect that the browser tab is either killed because of memory throttling, or because of some issue on the web-app I run. But so far I have traces to follow, to see if I’m right.
I have not been able to reproduce the issue locally, only in the production which is on a remote site.
Hardware: RevPi 3+
OS: balenaOS 2.53.9+rev1
Browser image: Docker Hub (
chromium-browser --version says
Web app: An online hosted React based app, communicating via MQTT with other systems.
The balena image on the machine is running 4 services: Browser, MQTT server (mosqitto), a node.js app to turn off display backlight when there’s no activity on MQTT, and a service that receives a webhook from an external device and forwards it to MQTT.
I’m also concerned whether I’m using an obsolete/outdated/broken browser image. I believe that I chose the
balenaplayground/balenalabs-browser image because it worked for me and the other images didn’t, but I’m not completely sure. But it bothers me that I cannot find the related github project and I cannot see how the image is composed. Neither balena playground · GitHub or balenaLabs · GitHub seems to have the
So maybe i’m better of with trying another browser image? Like the
balenablocks/browser which is also used by balena-dash?
Thanks in advance for any responses