balena sigsegv segmentation fault

Does this has something to do with corrupt memory?

When I try to execute any balena-engine command on one of my devices I get the followingo output:

unexpected fault address 0x1e58d00
fatal error: fault
[signal SIGSEGV: segmentation violation code=0x1 addr=0x1e58d00 pc=0x1f4f8]

goroutine 1 [running, locked to thread]:
runtime.throw(0x1245f86, 0x5)
/usr/lib/go/src/runtime/panic.go:616 +0x60 fp=0x13b6fefc sp=0x13b6fef0 pc=0x40b94
/usr/lib/go/src/runtime/signal_unix.go:395 +0x1bc fp=0x13b6ff20 sp=0x13b6fefc pc=0x574ac
runtime.mapassign_faststr(0x1060238, 0x13ba2080, 0x1245671, 0x5, 0x13bbead4)
/usr/lib/go/src/runtime/hashmap_fast.go:706 +0x34 fp=0x13b6ff60 sp=0x13b6ff24 pc=0x1f4f8
/usr/lib/go/src/unicode/tables.go:3447 +0x1044 fp=0x13b6ff90 sp=0x13b6ff60 pc=0xb51e0
:1 +0x4c fp=0x13b6ffa4 sp=0x13b6ff90 pc=0xccf98
:1 +0x4c fp=0x13b6ffb8 sp=0x13b6ffa4 pc=0xe2380
:1 +0x40 fp=0x13b6ffbc sp=0x13b6ffb8 pc=0xf16768
/usr/lib/go/src/runtime/proc.go:186 +0x1b8 fp=0x13b6ffe4 sp=0x13b6ffbc pc=0x42264
/usr/lib/go/src/runtime/asm_arm.s:1015 +0x4 fp=0x13b6ffe4 sp=0x13b6ffe4 pc=0x6e74c

Yes it could be. The kernel allocates memory on demand and if a process tries to access outside its allocation then you might see this error. Does this reoccur if you reboot?

yes it keeps happening after reboot

this could be a corrupted SD card then. If you have the device on balenaCloud then the “Diagnostics” action panel, on the left menu, might highlight some faults on the device.