[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <CA+TsHUAAybPKZZF4jXESa8sqKpfVyxF4C7L7uVmrzXMNPbHH7A@mail.gmail.com>
Date: Tue, 16 Sep 2014 22:58:06 +0530
From: Sayantan Datta <std2048@...il.com>
To: john-users@...ts.openwall.com
Subject: Re: memory issues: john is eating it all
On Tue, May 20, 2014 at 8:30 AM, Sayantan Datta <std2048@...il.com> wrote:
>
> On Tue, May 20, 2014 at 3:21 AM, Solar Designer <solar@...nwall.com>
> wrote:
>
>> 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.
>>
>
> I'll look into it ASAP.
>
> Regards,
> Sayantan
>
Fixed.
Regards,
Sayantan
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.
