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

[maykelbembibre]

Hashcat has got a feature which consists of updating a restore point periodically so that we can quit the task and then restore it at that point in the future, it is working with most of the hash types but specifically I can't get it to work with bcrypt hashes. The output I can see in this case is like the following. Restore point is always 0, it does never get updated, neither even when the task has been already finished, so with bigger dictionaries it is a serious problem, because when I restore a previously stopped task, its progress always starts from the beginning, regardless of the task having a very big progress when it was stoppped.

Code:

Session..........: test
Status...........: Exhausted
Hash.Type........: bcrypt, Blowfish(OpenBSD)
Hash.Target......: [there was a hash here]
Time.Started.....: Mon Feb 13 12:57:57 2017 (7 mins, 46 secs)
Time.Estimated...: Mon Feb 13 13:05:43 2017 (0 secs)
Input.Base.......: File ([a dictionary file path])
Input.Mod........: Rules ([a rule file path])
Input.Queue......: 1/1 (100.00%)
Speed.Dev.#2.....:      425 H/s (0.54ms)
Speed.Dev.#3.....:        0 H/s (0.00ms)
Speed.Dev.#*.....:      425 H/s
Recovered........: 0/1 (0.00%) Digests, 0/1 (0.00%) Salts
Progress.........: 198172/198172 (100.00%)
Rejected.........: 0/198172 (0.00%)
Restore.Point....: 0/2 (0.00%)
Candidates.#2....: [password] -> [password]
Candidates.#3....: [Copying]
HWMon.Dev.#2.....: N/A
HWMon.Dev.#3.....: N/A

[s]tatus [p]ause [r]esume [b]ypass [c]heckpoint [q]uit => Started: Mon Feb 13 12:57:55 2017

So, what's the matter with this? Is it a Hashcat bug? In that case, is it planned to be corrected at any specific release in the future?