0.83: Why this startup behavior after a crash?

[jadO]

On a fresh start or after a crash or something XnViewMP seems to access every single file in recursive folders upon start.
After it has done that, this behavior cannot be observed anymore. Swithing into other folders does not trigger it and going back to those folders where it happend does not trigger it as well.
I can only see it is accessing Thumb.db and XnView.db.

So why this initial access of all files in recursive folders, which is very time consuming?

[xnview]

There is no such access, if you don't view all files recursively in the browser

[jadO]

There is no such access, if you don't view all files recursively in the browser

This is what happend. I had my usual 0.83 hang and hat to close XnViewMP. As I had Process Monitor running to see what is happenng in case of a hang, I could see what happend.
Now when I started it I could see that it accesses every file in recursive folders. As it was right after start, I had not view all files enabled.

[xnview]

multiple tabs?

[jadO]

multiple tabs?

No, just one tab.

[xnview]

multiple tabs?

No, just one tab.

i think that it's sqlite update database with commands started before crash

[jadO]

i think that it's sqlite update database with commands started before crash

I don't know. This would mean that this action must have been triggered before the crash/hang.
But how can this be. As said it is a start up behavior, scanning only files in subfolders from start folder recursively and access all files that are in there.
This is not something I had triggered before the crash. So I don't know why Sqlite should do that.

Edit: I just thought maybe if I had show all recursive files enabled before the crash. Maybe this triggers this recursive search on start up after han?

[xnview]

To speed up, sqlite create a .journal file with all db insert. If the app crash, this .journal file is executed.