Duplicati database rebuild - 2gb client database for 750gb of backup files

Jumping into this topic for my own related question:

I am repairing because of an issue reported here
My repair has been runing for 12 hours.
I left duplicati gui running in chrome overnight with live log on, profile level.
I think chrome ate up 12 GB of virtual memory. I am not sure cuz it crashed and memory usage fell from 14GB to 2GB so I didnt actually see it. Something else may have also crashed releasing memory.
So Windows ran out of memory and things are acting strangely and I would normally reboot.
But, the repair is running…

This backup has 22GB source files and 13GB remote store.
Remote store has 2 or 3 versions only.

The green progress bar in the Gui has been at around 90% for 10 of the last 12 hours.
Here is an excerpt from the live log, profile level.
Can anyone tell how close it is to finishing? I assume it’s doing useful work because others have had their repair take days, but it might be nice to check that.

Enclosed: .excerpt from live log file, a zipped .txt file (5.4 KB)