Data in columns are not always displayed

Hi,

I'm displaying a lot of .doc files (800k) in flat folders view, and I can't get all files informations in the columns like "Last saved by" for instance. It does a few, then stops.

I also tried with exiftool scripts from (ExifTool Custom Columns) but it is the same.

The circle animation in the address bar never ends, and it only shows the data for the files currently displayed on screen.
If I scroll down or up, then it fills the column for the next files on screen, and after a while it doesn't do much and the column for all the remaining files stay empty, even if I scroll up and down.

Is there a limitation or something I can do to force the columns to be filled for all files ?

The script should be able to do it. You'll need a bit of patience for 800k files. Turn the log on and try with a few hundred to get a feeling for the speed. Might take a few hours to build the cache.

I don't think it is related to cache or to the script, as it happens without using the script and only using Directory Opus columns.

Also, my exiftool cache has exactly the same amount of files, so it has been generated properly. It is just that the data in the column don't work as they should.

I tried with fewer files (33k), and it is the same behavior.
The circle animation in the address bar never stops, and Directory Opus is playing lazy :slight_smile:
it only fetch and displays the currently displayed files. As soon as I scroll down, it wakes up and shows the following files, then goes for a nap again :slight_smile:
I have waited for hours, still the same behavior, it waits for me to scroll through all the files to display all fields. Which is ok with a few thousands files, but I can't scroll through 800k files.
48 files per page displayed in the lister, means 16k+ pages to scroll ! :crazy_face:

It sounds like either the background thread which reads the file information is getting stuck/delayed on some of the files, or some of the files cannot be accessed at all.

Opus itself doesn't read metadata from Word documents, so if something is stuck it's likely an external metadata DLL.

Process snapshots should allow us to see which component is getting stuck, and if it's something in Opus itself or external: Manually generating process snapshots

I'm trying again today, I'll upload the dumps if I can't find any solution.
Is there at least a way to have more information about how far it has advanced gathering additional informations ?
Is there a way to have a % instead of the spinning circle ?
I'm currently checking with disk ressource monitor to see the file name currently accessed... not ideal.