Something is wrong and I cannot figure out what/why

[serrato]

I updated from the 1.5a versions to 1.5b yesterday. Around the same time (unfortunately cannot remember if before or after update, since both were done around the same time), I added a format (.m4v) to the Properties index. Before this, everything has been indexed for a long time now.

But now one thread of my CPU is always maxed out (this may be unrelated), and in Options, there is that upper right corner thing showing "Indexing:" and it's almost always my C drive and almost always the Local folder, ESPECIALLY the Temp folder. Even reducing the temp folder to around 1 GB (can't removed everything as stuff running needs it), it's still indexing this folder. But why? The C drive is possibly the least-changed drive, and even if it does change, it's the fastest drive (NVME) and also the least amount of data is on it. So what's going on? Because of this, I'm suspecting I'm having other issues with my thumbnails suddenly being broken and no amount of explorer restarts fixes it, but it may be unrelated.

The other weird thing is that if I make a change in these indexing properties, I'll get the *actual* indexing bar underneath in the bottom right of the main window, and once it's done, you'd expect it's done, but then in options that small top right corner still keeps showing something being indexed. Again, in Temp. Why are there two different indexing "meters", so to speak, this latter one having no progress bar, so I cannot tell when it will be done. It's confusing enough that I can't really word everything properly lol.

[void]

Please send your Help -> Troubleshooting information.

[serrato]

PM'd you my troubleshooting info

At the very least I figured out the one-thread-maxing out thing - it was COM Surrogate stuck in something and that was also causing the thumbnails issue as expected. So thankfully only the forever indexing thing left.

[void]

Thanks for the troubleshooting information.

I suspect it's the trailing ; in your include only files and child count from disk indexing causing troubles.

Please try the following:
Under Tools -> Options -> Properties
Select Audio Bit Rate
Change Include only files from:

*.flac;*.mp3;*.wav;*.ogg;*.mkv;*.mp4;*.avi;*.flv;*.webm;*.wmv;*.iso;*.isoJAV;*.m4v;

to:

*.flac;*.mp3;*.wav;*.ogg;*.mkv;*.mp4;*.avi;*.flv;*.webm;*.wmv;*.iso;*.isoJAV;*.m4v

(remove trailing ; )

Do not index Child Count From Disk, Child File Count From Disk, Child Folder Count From Disk.
Please remove these from your property index.
Everything will constantly be indexing these properties.
Everything automatically indexes Child Count, Child File Count and Child Folder Count.
Use those properties instead.

Select Dimensions
Change Include only files from:

*.jpg;*.png;*.gif;*.tif;*.tiff;*.mkv;*.mp4;*.avi;*.flv;*.webm;*.wmv*.m4v;

to:

*.jpg;*.png;*.gif;*.tif;*.tiff;*.mkv;*.mp4;*.avi;*.flv;*.webm;*.wmv;*.m4v

(remove trailing ; and add a ; after *.wmv)

Select Frame Rate
Change Include only files from:

*.mkv;*.mp4;*.avi;*.flv;*.webm;*.wmv*.m4v;

to:

*.mkv;*.mp4;*.avi;*.flv;*.webm;*.wmv;*.m4v

(remove trailing ; and add a ; after *.wmv)

Select Total Bit Rate
Change Include only files from:

*.mkv;*.mp4;*.avi;*.flv;*.webm;*.wmv*.m4v;

to:

*.mkv;*.mp4;*.avi;*.flv;*.webm;*.wmv;*.m4v

(remove trailing ; and add a ; after *.wmv)

Select Video Bit Rate
Change Include only files from:

*.mkv;*.mp4;*.avi;*.flv;*.webm;*.wmv*.m4v;

to:

*.mkv;*.mp4;*.avi;*.flv;*.webm;*.wmv;*.m4v

(remove trailing ; and add a ; after *.wmv)

[serrato]

Thanks! I wasn't sure of the trailing edge but then when adding m4v I copied the previous one and pasted the mistake over and over again.

[void]

Actually, the trailing ; is ignored.
I suspect the issue is really caused by indexing Child Count From Disk, Child File Count From Disk and Child Folder Count From Disk.

I ran your config here without any issues.

[serrato]

Cool, so I guess for now this is solved!

[Herkules97]

The other weird thing is that if I make a change in these indexing properties, I'll get the *actual* indexing bar underneath in the bottom right of the main window, and once it's done, you'd expect it's done, but then in options that small top right corner still keeps showing something being indexed. Again, in Temp. Why are there two different indexing "meters", so to speak, this latter one having no progress bar, so I cannot tell when it will be done. It's confusing enough that I can't really word everything properly lol.

The main point seems to have been answered, but as Void didn't answer this..
It's most likely that it's just re-indexing existing files.
If you index property A for 10K files, then add property B for those 10K+5K new files, 5K will be shown in the progress bar because those are new and 15K will be shown in the options window, I believe.
Or some combination of the progress bar only showing new files, new properties and old files.
And options menu maybe a combination of all 4, new files, old files, new properties, old properties.
Progress bar can be stuck at 99% if new files are at the bottom of the queue list as it is going through new/old files before those. I don't think you can currently see the queue.

It may have been done this way so it doesn't constantly pop up the progress bar when new files are made after the queue is originally done. As in day-to-day operations, the progress bar doesn't show up and only shows up when a rebuild takes place from say adding new NTFS/FAT devices or folders.

[void]

Yes, the progress bar is only shown after a reindex.
Once the property request queue is empty, the progress bar is hidden.

There's two queues, a background and foreground queue.
The foreground queue is processed first, then the background queue.
Requests from a reindex are added to the background queue.
Requests after a reindex are added to the foreground queue.