TestMetricsandPprofExist timedout and crash

[geyslan]

make test-performance:

-test.shuffle 1736783919560271707
=== RUN   TestMetricsandPprofExist
    metrics_test.go:121: tracee timedout to start
    panic.go:626: found unexpected goroutines:
        [Goroutine 9 in state select, with github.com/aquasecurity/tracee/tests/testutils.ExecCmdBgWithSudoAndCtx.func2 on top of the stack:
        github.com/aquasecurity/tracee/tests/testutils.ExecCmdBgWithSudoAndCtx.func2(0xc0003f6ee8)
        	/tracee/tests/testutils/exec.go:165 +0xdd
        created by github.com/aquasecurity/tracee/tests/testutils.ExecCmdBgWithSudoAndCtx in goroutine 7
        	/tracee/tests/testutils/exec.go:164 +0x866
         Goroutine 19 in state syscall, with syscall.Syscall6 on top of the stack:
        syscall.Syscall6(0xf7, 0x1, 0x2c394, 0xc000082d90, 0x1000004, 0x0, 0x0)
        	/home/tracee/go/pkg/mod/golang.org/[email protected]/src/syscall/syscall_linux.go:91 +0x45
        os.(*Process).blockUntilWaitable(0xc0000d4000)
        	/home/tracee/go/pkg/mod/golang.org/[email protected]/src/os/wait_waitid.go:32 +0x9f
        os.(*Process).wait(0xc0000d4000)
        	/home/tracee/go/pkg/mod/golang.org/[email protected]/src/os/exec_unix.go:22 +0x4b
        os.(*Process).Wait(...)
        	/home/tracee/go/pkg/mod/golang.org/[email protected]/src/os/exec.go:134
        os/exec.(*Cmd).Wait(0xc000337b80)
        	/home/tracee/go/pkg/mod/golang.org/[email protected]/src/os/exec/exec.go:897 +0xb9
        github.com/aquasecurity/tracee/tests/testutils.ExecCmdBgWithSudoAndCtx.func1.1()
        	/tracee/tests/testutils/exec.go:143 +0x8f
        created by github.com/aquasecurity/tracee/tests/testutils.ExecCmdBgWithSudoAndCtx.func1 in goroutine 8
        	/tracee/tests/testutils/exec.go:140 +0x31a
        ]
--- FAIL: TestMetricsandPprofExist (10.99s)
FAIL
FAIL	github.com/aquasecurity/tracee/tests/perftests	71.452s
FAIL

Originally posted by @ShohamBit in #4485 (comment)

[ShohamBit]

I suspect this issue is related to available hardware resources, particularly RAM. My machine has 16GB of RAM, and I often observe high RAM usage (consistently above 80-85%), even before running the Tracee tests. This suggests that memory constraints might be impacting the compilation process,