Termux arm64 memory leak or too high memory usage

[VinkyV]

Environment

Android 15 aarch64 + Termux 0.119.0-beta.1
$ r2 -v
radare2 5.9.8 0 @ linux-arm-64
birth: git.5.9.8 2024-11-19__12:16:54
commit: 5.9.8
options: gpl release -O1 cs:5 cl:2 make
$ uname -ms
Linux aarch64

Windows 10 amd64
$ r2 -v
radare2 5.9.8 1 @ windows-x86-64
birth: git.5.9.8 Tue 11/19/2024_11:46:03.42
commit: 4eb49d5
options: gpl -O? cs:5 cl:1 meson

Description

Tried to analyze minecraft Bedrock Edition server software Linux amd64 but on aarch64 on Android I always get sigmentation fault or Aborted.

Tried analyze on the amd64 and it succeed.

Expected: successful analyze

Both have 16 gb of Ram & enough storage.

Test

Download https://www.minecraft.net/en-us/download/server/bedrock
run r2 -e bin.relocs.apply=true bedrock_server
In radare2 run aaa or aac

[VinkyV]

Windows 10 max memory usage not exceeded 8GB during the entire analysis.
When the Android 15 exceeded 10GB on aac step and was killed.

[trufae]

Try r2 from git. Last release is quite old

[VinkyV]

~/downloads $ r2 -e bin.relocs.apply=true bedrock_server
-- Remember to maintain your ~/.radare_history
[0x03307280]> aac
Aborted
~/downloads $ r2 -v
radare2 5.9.9 33579 @ linux-arm-32
birth: git.5.9.8-551-g1a3cdec82e 2025-04-08__15:54:55
commit: 1a3cdec
options: gpl -O? cs:5 cl:2 make

And sys/install.sh installed me an arm-32 version instead of arm-64

[trufae]

its a 200MB executable, is quite normal that the analysis takes a lot of memory. also, considering that you are analyzing the 32 bit its more than normal that memory consumption can explode quickly. i would recommend you to analyze the arm64 binary instead. in my linux box this takes 4GB of ram only. and i see nothing strange with heaptrack.

the reason for the crash in your linux-arm32 is probably because you are using debian which have a very restrictive memory layout and kernel configuration that kills any process that takes a lot of memory.

is your system supporting both arm32/arm64 ? thats weird, can you show me the output of uname -a?.

[VinkyV]

its a 200MB executable, is quite normal that the analysis takes a lot of memory. also, considering that you are analyzing the 32 bit its more than normal that memory consumption can explode quickly. i would recommend you to analyze the arm64 binary instead. in my linux box this takes 4GB of ram only. and i see nothing strange with heaptrack.

Im trying analyze x86 binary I mean strange that radare2 on my windows machine eating lower than 8 GB but when I am trying analyze the same binary it's slowly consuming more more and more after reaching almost 12 gb of ram it will be killed also android extended ram not helps.
It's only on termux build.

the reason for the crash in your linux-arm32 is probably because you are using debian which have a very restrictive memory layout and kernel configuration that kills any process that takes a lot of memory.

It's crashing on both linux-arm-64 & 32 I just builded radare2 from scratch and somehow it builded and installed 32 bit version. And it's android not Debian, and I don't see any restriction in memory layout cuz 4 gb eaten by my system and 12gb by radare2.

is your system supporting both arm32/arm64 ? thats weird, can you show me the output of uname -a?.

~/radare2 $ uname -a

Linux localhost 6.6.30-android15-8-g54dcbfbef792-ab12368803-4k #1 SMP PREEMPT Fri Sep 13 17:41:25 UTC 2024 aarch64 Android

[AbhiTheModder]

Just saw this, if in case it still persists, this can help to solve it. Enable "Disable child process restrictions" option from developer options.

More on this here: https://github.com/agnostic-apollo/Android-Docs/blob/master/en/docs/apps/processes/phantom-cached-and-empty-processes.md

Leaving it here for future references