Why doesn't the restore point update with BCrypt hashes?

[maykelbembibre]

That's because you did check only 348 words yet (28780880 / 82563). You threads alone do 256, not even counted the shader or the -n multiplicator. For sure you didn't reach a checkpoint for restore. Problem is not hashcat here, problem is cracking 82563 at once is braindead

There is still a problem. I tried with a task with a ten thousand words dictionary, waited for 18 hours, and then, when progress was at 27%, I saw that still there was not any restore point:

Code:

Session..........: 647c1801-f925-4e85-8af1-b68e161d4ba1
Status...........: Running
Hash.Type........: sha512crypt, SHA512(Unix)
Hash.Target......: [hashes file]
Time.Started.....: Tue Feb  7 15:17:38 2017 (18 hours, 9 mins)
Time.Estimated...: Fri Feb 10 08:40:42 2017 (1 day, 23 hours)
Input.Base.......: File ([dictionary file])
Input.Mod........: Rules ([rule file])
Input.Queue......: 1/1 (100.00%)
Speed.Dev.#1.....:    17139 H/s (1.30ms)
Speed.Dev.#2.....:    17490 H/s (1.25ms)
Speed.Dev.#*.....:    34628 H/s
Recovered........: 6/10615 (0.06%) Digests, 6/10615 (0.06%) Salts
Recovered/Time...: CUR:0,0,N/A AVG:0,0,7 (Min,Hour,Day)
Progress.........: 2286481455/8173550000 (27.97%)
Rejected.........: 817355/2286481455 (0.04%)
Restore.Point....: 0/10000 (0.00%)
Candidates.#1....: kangaro -> boeing74
Candidates.#2....: 1234 -> weltmeist
HWMon.Dev.#1.....: Temp: 78c Fan: 66% Util: 95% Core:1124Mhz Mem:2505Mhz Lanes:16
HWMon.Dev.#2.....: Temp: 71c Fan: 58% Util: 94% Core:1124Mhz Mem:2505Mhz Lanes:16

I know that Hashcat does not create a restore point until it finishes checking the current dictionary blocks. This time if we look at the candidates, we can know that the ten thousand words dictionary was divided into two blocks of five thousand words and then the two blocks got executed simultaneously. That's because the 1st word of the dictionary was "123456", the number 5000 was "weltmeister", the number 5001 was "kangaroo", while the last, number 10000 was "boeing747". I work out that this time Hashcat won't create a restore point until the whole dictionary is checked. Isn't that a little kind of nonsense?