balenaOS 6.5.2 hangs with 100% CPU load on BeaglePlay

After initially providing some interaction, now the OS locks up shortly after reboot. I’m going to try to add more boards to see if it is board-specific. Let me know if there is more information I can provide, but it seems currently the OS release is not usable.

Mem: 1743304K used, 232836K free, 6308K shrd, 41984K buff, 1267876K cached
CPU:   0% usr   0% sys   0% nic  99% idle   0% io   0% irq   0% sirq
Load average: 0.92 1.17 0.54 2/272 3194
  PID  PPID USER     STAT   VSZ %VSZ %CPU COMMAND
 2397     1 root     S    1457m  75%   0% /usr/bin/balena-containerd-shim-runc-v2 -namespace moby -id XXXX -address /var/run/balena-engine/c
 3086  3080 root     R     3620   0%   0% top
 1587  1552 root     S    1458m  75%   0% balena-engine-containerd --config /var/run/balena-engine/containerd/containerd.toml --log-level info
 2675     1 openvpn  S     9428   0%   0% /usr/sbin/openvpn --writepid /run/openvpn/openvpn.pid --cd /etc/openvpn/ --config /etc/openvpn/openvpn.conf --connect-retry 5 120
  919     2 root     IW       0   0%   0% [kworker/0:11-ev]
 2418  2397 root     S    10.4g 553%   0% node /usr/src/app/dist/app.js

I got the above from top on a fresh unit. Still working fine for now, but why is app.js taking up so much virtual memory?

Anyway, I’m up-and-running for now with this second unit, but would love to diagnose what is happening to the other one. There’s always a chance I grabbed a prototype unit.

On the “bad” device, I was eventually able to see the CPU load drop back down to below 50%. When trying to access the terminal, it kept connecting and then disconnecting.

Connecting to XXXXX...
SSH session disconnected
SSH reconnecting...
SSH session disconnected
SSH reconnecting...
SSH session disconnected
SSH reconnecting...
SSH session disconnected

I thought perhaps this could be to having multiple VPN connections, so I unplugged the Ethernet cable (still connected via WiFi), but this seemed to make no difference.

It could have been I had a bad app, but not sure how. Anyway, the problem just went away.

Happy to hear you figured this out! Please let us know if you get stuck again