Is there some upper limit on the number of thumbnails that can be displayed (some off screen perhaps) at one time? I have one directory with subdirectories that are loaded with images. Over 15,000 at last count. I like to do flat view on this directory and run slideshows of the images. I've been doing this for ages without problem.
I recently added maybe a couple thousand more images to the subdirectories. Now when I do the flat view slideshow, the disk goes crazy for a while, settles down a bit, then goes crazy again and DOpus ends up telling me the installation is corrupted.
I've downloaded a new copy and reinstalled it, but I get the same result. Funny thing is, it doesn't complain about the corrupted installation until it's been running for probably 15 minutes. You'd think a corrupted install check would be done first thing when the program starts.
I tend to think the installation is not actually corrupted. And since it's done this only when I have the vast number of thumbnails displayed, I have to think there's some kind of connection. Any ideas?
DOpus is supposed to claim it's corrupted when Windows starts paging?
I only mentioned the disk activity because it's what I observed and it consistently coincided with the corrupted program popup. You may well be right that the second spurt of disk activity is Windows paging, though I'm not sure why it would suddenly go crazy paging after 15 minutes of slideshow.
I've now had DOpus running for about 20 minutes without the massive number of thumbnails being displayed and there have been no claims that the program is corrupt. I still have to think there's some connection between the 15k+ files and this problem.
Have a look at Task Manager when you go into Flat View on that folder. You should see the available memory drop as all the thumbnails are loaded. (Depending on your Thumbnail mode settings, Opus may be loading up to 256x256 versions of each image into memory.) If your machine is running out of physical memory and then also running out of page file then you could get weird behaviour in Opus and other apps.
Turning off the option which tells Opus to load all thumbnails automatically (so that it instead only loads things when they are in view) may help. (Or avoid viewing huge folder as thumbnails in Flat View.)
You can rule out a actual corrupted install by going to /home (which is an alias that takes you to the Opus Program Files folder) and bringing up Properties on dopus.exe and dopuslib.dll. In the Properties dialog, click on the Digital Signatures tab and then click Details. You should see a "Digital Signature Details" window open where it will say "This digital signature is OK."
Both files say the digital signatures are okay, so it doesn't look like actual corruption is an issue.
Memory usage did go to 1.51GB and, if I'm reading it right, the paging file did come in to play, but peaked at 1.6GB. It starts at 2GB and is allowed to grow to 4GB. The drive the pagefile is on has 32GB available.
The thumbnails are 128x128 and I have it configured to generate only the thumbnails of that size. (Dynamic thumbnail resizing is disabled.)
The thumbnail cache is set to a max size of 8GB. The current size is 6.3GB.
All these numbers are after doing a flat view on that same directory and starting a slideshow. So far I have not seen the second spurt of disk activity and no corrupt program popup.
I had thought 2GB would be plenty of memory, but after this little exercise I'm thinking it might be time to populate the other two slots that are still open on the motherboard. Memory has gotten so cheap there's almost no reason not to.
I'll post again if I gather any more information that might be useful.
If you're using 32 bit Windows then any individual process can only allocate 2 GB of memory, so adding more RAM will not necessarily help with this unfortunately.
According to task manager DOpus never exceeded roughly 600MB, at least according to the Mem Usage column. I had another very large memory hog running at the same time. That's why the memory in use hit 1.6GB.
I was seeing the same issue when the other memory hog wasn't running.
I have sitting beside me another 2GB of memory that was just delivered. I'll install it tonight and give the same thing another try. For $24 delivered (after $20 rebate) there seemed little reason not to add another 2GB.
I just discovered something about the thumbnail cache. The directory labeled as the cache contains 116,418 files.
I was verifying that the exclusion of that directory from my virus scan was still set up correctly. Whenever I tried to pull up the directory path to inspect it, I'm guessing the virus scanner went to do some kind of verification on the directory and hung up. I suspect it might have returned eventually if I was willing to wait however long it takes to scan through 116,000 files.
I don't know that this has anything to do with the problem I ran into before, but it sure seems suspicious. 116,000 files in one directory is a LOT of files. Sure seems like it might be a tad more efficient, file system-wise, to use something more like a real database for storing the thumbnails. Something that would keep a lot more data in a single file. From the size of these I'm guessing it's not one file per thumbnail. Is it one thumbnail file per directory? I didn't think I had quite that many directories.
Oh, I bet it's because I'm using a lot of junctions and links. In several cases this leaves me with multiple paths to the same directories. It's probably creating multiple copies of many of the thumbnails and directories.