confirmed value equals to unconfirmed at some point

[vlddm]

First {confirmed: 0, unconfirmed: 1000}
Then {confirmed: 1000, unconfirmed: 1000}
Next {confirmed: 1000, unconfirmed: 0}
Looks like it happens in the moment of first confirmation.
Im using 1.12.0 on Litecoin mainnet.
Not happens all the time, doing huge amount of requests on different addresses and just few of them returns doubled results.
Looks like transactions adding in UTXO list and removed from mempool in a not atomic way so can count on both confirmed and unconfirmed balances for some unlucky users.

[wedevelopio]

Bounty USD$100

[kyuupichan]

Yes it's not currently atomic; requests are served concurrently to block processing, and mempool processing is also concurrent. I'm not sure if there is an easy fix; simply pausing all requests while a block is processed is not acceptable

[dmitry537]

Any fixes? This is critical.