@ARx8 @rafaeldavid
I was having this problem, and I just figured out that this is a cheat from the chip.
I don't know the details but basically they mark the memory as 2GB but it actually just have 512MB.
The Armbian sees 2GB but when you do a task that requires more that the actual 512MB it crashes.
To solve that I manually set the memory on the Armbian to be 512MB.
Edit the file:
/boot/armbianEnv.txt
Add the line (or change if already exists):
extraargs=mem=512M
On my case the device claimed 2GB of Ram. I reach the 512M testing.
To get to this number I ran:
free -h
This gave me the amount of memory the system was already using (230M).
After that I apt installed memtester and start testing the memory:
memtester 200M
I started at 200M and cancel the test (CTRL-C) on the firsts interaction after:
Stuck Address : ok
Random Value : ok
Compare XOR : ok
Compare SUB : ok
Compare MUL : ok
Compare DIV : ok
Compare OR : ok
Compare AND : ok
The other tests took too long and if the problem is the memory that didnt exist just the firsts test would be enough.
I ran memtester increading by 50M, so 200,250,300... And on 300 the system crashed, so I assumed the real memory of the
chip was 512 (the 230 from the system + the 250 from the memtester before it crashed).
