Date: Tue, 20 May 2014 01:51:02 +0400 From: Solar Designer <solar@...nwall.com> To: john-users@...ts.openwall.com Subject: Re: memory issues: john is eating it all On Mon, May 19, 2014 at 09:44:06PM +0000, yungai wrote: > I've got an issue with john's memory usage. > After a few days, max. a weak, I have to stop->resume john because he > uses all of the 16GB of RAM and ~20% of available swap. > > It is a opencl gpu cracking job attacking traditional DES crypt hashes. > > I'm using bleeding-jumbo from 2014-04-17. > > Can anyone confirm this problem? Yes, descrypt-opencl appears to be leaking memory. In the recent contest, I was running "--format=descrypt-opencl --fork=4" on a 7970 (the --fork=4 results in much greater performance at this format, since otherwise the GPU would stay mostly idle waiting for data from host). This consumed about 6 GB of RAM (about 1.5 GB per forked process) in about 10 hours. I was going to report it to Sayantan on john-dev, but you were quicker to bring the same issue up. Alexander
Powered by blists - more mailing lists
Confused about mailing lists and their use? Read about mailing lists on Wikipedia and check out these guidelines on proper formatting of your messages.