出现系统内存不足

[wanli0]

root@ec65a6bc90ad:/SnapFuzz-artefact/results-snapfuzz-dns-2023-12-11-03-17# cat output-dns-1.2.txt
afl-fuzz 2.56b by lcamtuf@google.com
[+] Looks like we're not running on a tty, so I'll be a bit less verbose.
[+] You have 256 CPU cores and 4 runnable tasks (utilization: 2%).
[+] Try parallel jobs - see docs/parallel_fuzzing.txt.
[] Checking core_pattern...
[] Checking CPU scaling governor...
[] Setting up output directories...
[] Scanning './conf/in-dns'...
[+] No auto-generated dictionary tokens to reuse.
[] Creating hard links for all input files...
[] Validating target binary...
[+] Deferred forkserver binary detected.
[] Attempting dry run with 'id:000000,orig:dns_queries.raw'...
[] Spinning up the fork server...
[+] SaBRe handshake OK!

[-] Whoops, the target binary crashed suddenly, before receiving any input
from the fuzzer! There are several probable explanations:

- The current memory limit (512 MB) is too restrictive, causing the
  target to hit an OOM condition in the dynamic linker. Try bumping up
  the limit with the -m setting in the command line. A simple way confirm
  this diagnosis would be:

  ( ulimit -Sv $[511 << 10]; /path/to/fuzzed_app )

  Tip: you can use http://jwilk.net/software/recidivm to quickly
  estimate the required amount of virtual memory for the binary.

- The binary is just buggy and explodes entirely on its own. If so, you
  need to fix the underlying problem or find a better replacement.

- Less likely, there is a horrible bug in the fuzzer. If other options
  fail, poke <lcamtuf@coredump.cx> for troubleshooting tips.

[-] PROGRAM ABORT : Fork server crashed with signal 11
Location : init_forkserver(), afl-fuzz.c:3374