+- hashcat Forum (https://hashcat.net/forum)
+-- Forum: Support (https://hashcat.net/forum/forum-3.html)
+--- Forum: hashcat (https://hashcat.net/forum/forum-45.html)
+--- Thread: hashcat64 4.2.1 getting killed OOM (/thread-7813.html)
hashcat64 4.2.1 getting killed OOM - mahoganyduck - 09-17-2018
Hello!
With the latest version of hashcat, when I try to run a benchmark it runs for a moment then gets killed pretty fast (4-5 sec) while starting the MD5 benchmark.
Earlier versions of hashcat haven't had this issue.
[ 1606.609541] [17230] 0 17230 5719 545 94208 0 0 bash
[ 1606.609542] [17602] 0 17602 5717 542 94208 0 0 bash
[ 1606.609543] [ 8523] 0 8523 24787695 1767959 15208448 0 0 hashcat64.bin
[ 1606.609543] [ 8776] 0 8776 1128 20 57344 0 0 sh
[ 1606.609544] [ 8784] 0 8784 1128 24 57344 0 0 sh
[ 1606.609544] [ 8785] 0 8785 15926 2935 167936 0 0 minerfarm_svc
[ 1606.609545] [ 8786] 0 8786 1826 18 53248 0 0 fold
[ 1606.609546] Out of memory: Kill process 8523 (hashcat64.bin) score 876 or sacrifice child
[ 1606.609591] Killed process 8523 (hashcat64.bin) total-vm:99150780kB, anon-rss:6573256kB, file-rss:474004kB, shmem-rss:24576kB
[ 1606.683961] oom_reaper: reaped process 8523 (hashcat64.bin), now anon-rss:0kB, file-rss:380kB, shmem-rss:0kB
System:
6x gtx 1070 driver 384.98
8G ram
Intel(R) Core(TM) i3-7350K
(yes it's a mining rig)
It's worked like a *champ* until this release (about a year).
Obviously it wouldn't hurt to throw more ram and a better proc at it, but for now I'm looking for an explaination on what changed in this version; if there's any tuning I can do either with a hashcat config switch; tuning linux itself.
Thanks!
RE: hashcat64 4.2.1 getting killed OOM - soxrok2212 - 09-17-2018
Are you using the binaries from here or the latest git? If you're using the binaries here, try compiling the latest git. Additionally, I think linux has 390.? support, might want to try updating your drivers, though it doesn't necessarily seem like a driver problem.
RE: hashcat64 4.2.1 getting killed OOM - undeath - 09-17-2018
Ideally you have as much RAM as you have VRAM. The lower limit for available system RAM hashcat requires was set to 2GB per opencl device if I remember correctly. (thus, running with only three devices should not trigger the OOM killer)