Poor Memory Optimization when saving large Projects

[rectrap]

Description

I was analyzing a large binary (~70MB) and wanted to save the session after I had executed "aa", "aaa", and "aaaa" because they took quite some time, running "Ps".

r2 exited with "killed" due to being out of memory, as evident by the dmesg

[2881260.202621] Out of memory: Killed process 454123 (r2) total-vm:7042300kB, anon-rss:6668924kB, file-rss:264kB, shmem-rss:0kB, UID:1000 pgtables:13336kB oom_score_adj:0

I'd like to suggest better memory management during large file operations. I do not know the internals of radare2, but it feels it could be improved.

[trufae]

Try the new projects. With the prj command.

I wrote this thibg 3 years ago with all those problwms in mind and im still waiting for some feedback. I plan to replace the script based projects with this as soon as they are tested enough. Hopefully 2026 is the year?

[rectrap]

Thanks

[rectrap]

Btw, in the [file] argument of the prj command, is there a way to add home relative paths with "~", because it is mistaking it with the control character I think.

[trufae]

like in any other command in r2 the ~ char is the internal filter. you can start the command with a single quote 'prj ~/foo and it should work

[rectrap]

Thx!

[trufae]

can you provide a backtrace when this OOB happens?

[rectrap]

gdb.txt
Is this satisfactory?