search

bee-san / Ares

Automated decoding of encrypted text without knowing the key or ciphers used
MIT License
575 stars 28 forks source link

[BUG] Killed after x seconds #313

Open be4zad opened 1 year ago

be4zad commented 1 year ago

I think Ares uses a lot of RAM or CPU.

OS: Debian GNU/Linux trixie/sid x86_64 RAM: 3698MiB CPU: Intel i3 M 330 (4) @ 2.133GHz

…

15 seconds have passed. 15 remaining                                                    20 seconds have passed. 10 remaining                                                    25 seconds have passed. 5 remaining                                                     Killed
BoxHezi commented 2 months ago

Same problem here, but instead of a killed, I get terminated signal SIGKILL

OS: openSUSE-Tumbleweed on WSL2 RAM: 8GB CPU: AMD Ryzen AI 9 HX 370

ares -t "LJIVE222KFJGUWSRJZ2FUUKSNNNFCTTLLJIVE5C2KFJGWWSRKJVVUUKOORNFCUTLLJIVE222KFHH
IWSRKJVVUUKSNNNEOUTULJIU4222KFJGWWSRJZ2FUUKONNNFCTTKLJIU45C2KFJGWWSHJZVVUR2SORNFCUTLLJI
VE222I5JHIWSRKJVVUR2ONJNEOTTULJIVE222KFJGWWSRJZ2FUUKSNNNFCTTLLJIU45C2KFHGWWSRJZVFUUKSHU
======" -d
5 seconds have passed. 25 remaining
10 seconds have passed. 20 remaining
fish: Job 1, 'ares -t "LJIVE222KFJGUWSRJZ2FUU…' terminated by signal SIGKILL (Forced quit)

I also use htop to check for CPU and RAM usage during running ares, before SIGKILL signal, my CPU usage goes up to 100%. image