Missing suggestions in the right-click context menu

GlikeG

Hi Andrey,

Recently, I can’t specify an exact point in time (other than within the last two weeks) or reason,
Tonfotos stopped listing suggestions in the right-click context menu in the photo preview.
In this context menu, I see only the name of the last manually tagged person.

I have around 300 people, each with hundreds of photos. This was working fine for quite a while.
Tonfotos is still recognising new faces and suggests assignments to people.
The only thing is that I have recently added a much newer graphics card (ASUS GeForce GT 1030 2GB GDDR5) to ensure it fully supports CUDA functionalities.
Currently, I’m running two dedicated graphics cards (above ASUS + MSI GeForce GTX 750 OC V1 1GB GDDR5 128Bit), and one integrated on the motherboard.

I appreciate any help you can provide.

GlikeG

In debug logs, I see it tries to build a list of suggestions by reading a list of disk drives, and it stops there:

+948ms | best_person_candidate_for_face: Init buffer
+70ms | get_sources_paths: {
‘1736778676970’: ‘A:\photos’
} read-only: {}
+1031ms | [
{ disk: 0, partition: 1, volume: ‘A:’ }
]
+419ms | [
{
mount: ‘A:’,
dev: ‘\\?\Volume{a-b-c-d-e}\’,
flags: [ ‘A’ ],
volume_name: ‘AAA’,
volume_fs: ‘exFAT’,
volume_sn: 123,
volume_size: 456
}
]

Andrey

GlikeG Most likely, recognition data cache was dropped, but that is OK. Program keeps all the data needed for face suggestions in the separate cache for fast access and stores it on the disk when exited. However, if program crashes or is forcefully closed, it can’t flush it to the disk and at the next start it will have to reacreate if from the scratch by reading data from DB in the background. All you need to do is to wait for several minutes (yes, it can take some time, lots of data to read) and then it will start working normal.

GlikeG

Later on, in logs, I have noticed that it is rebuilding the DB.
Maybe it would be worth presenting DB status (green - ready, yellow with percentage - progress) somewhere in the GUI?

Andrey

GlikeG It is not rebuilding DB, it is rebuilding cache from DB, as I explained above. This sort of self-healing procedure, but it is not supposed to happen in normal situations. That is why there is no indication in UI - we are not expecting that users will face this that often.

GlikeG

Andrey

In this case, perhaps the closing procedure is failing, and something is happening in the wrong way.
I didn’t notice any crashes recently, so it’s hard to share something unusual that can trigger such behaviour.