[BUG] nuclei command Unexpected exit

[Stitchez]

Is there an existing issue for this?

• I have searched the existing issues.

Current Behavior

nuclei command Unexpected exit

Expected Behavior

scan success

Steps To Reproduce

echo "test.com" > /data/2025-04-22/list.txt 
nuclei -list /data/2025-04-22/list.txt -severity medium,high,critical   -stats -stats-interval 5 -je /data/2025-04-22/nuclei-results.json -elog /data/2025-04-22/nuclei-error.log

Relevant log output

Environment

- OS: Linux 5.10 amd64
- Nuclei:  v3.4.2
- Go: 1.23.1

Anything else?

No response

[Frodothedwarf]

To add to this, I've had similiar issues on GitHub Workflows.

On the GitHub hosted runners it exits with this code:
The runner has received a shutdown signal. This can happen when the runner service is stopped, or a manually started runner is canceled.

And on self-hosted runners it exits the runner itself with a "OOM-killer".
Nuclei is taking all the ram of the machine, I looked into the ram usage on the machine itself, and Nuclei used 24GB of ram.

These are with the official Nuclei action.

[Linux-MMA]

I can't finish any of my scans as well. Sometimes the process quits unexpectedly, and other times Zsh kills the process. This happens at different stages of the scan. I’m running a few targets simultaneously while using TMUX. I checked the CPU usage and RAM, and it took about 40% and 50%, but sometimes the CPU usage jumped much higher. I run my scans from a VPS. Additionally, the -resume flag doesn't seem to work as intended. I can't restart the scans from the stopping point.

[ehsandeep]

A fix for this issue being devloped in #6193