I have a file collection with 2040 items.
viewing the collections is so slow its unusable.
taskmanager shows low cpu and memory use while
Dopus.exe occasionaly shows "not responding" as
it tries to show file collection.
What should i do to troubleshoot?
What kind(s) of files are in the collection?
Does it point to things on local disks, or on network servers?
All on local disk.
all are image files. Mostly Jpg Png Gif
and a few PSD (photoshop files).
Now Dopus is using 25% of cpu & i dont even have a lister open.
While it's happening, please go to Task Manager, then the Details tab, right-click dopus.exe and select Create Dump File.
Do that 4 or 5 times, and it should create something like:
C:\Users\<username>\AppData\Local\Temp\dopus.DMPC:\Users\<username>\AppData\Local\Temp\dopus (2).DMPC:\Users\<username>\AppData\Local\Temp\dopus (3).DMPC:\Users\<username>\AppData\Local\Temp\dopus (4).DMPC:\Users\<username>\AppData\Local\Temp\dopus (5).DMPPlease zip those up and email them to crashdumps@gpsoft.com.au
Can i find out whats wrong by looking at the dumps myself.
What should i look for?
theyre huge 500mb to 1gig.
I have noticed that some of my collections have become corrupted. with the filenames
just being unrecognized symbols with a size of 0 bytes. Do i have to worry about my files becoming corrupted?
Possibly. Try loading them into Visual Studio and see what is in the stack trace. (If that doesn't mean anything to you, then probably not. :))
They usually compress very well, which is why we say to zip them before emailing them.
Could you post a screenshot of what you are seeing?
The collections themselves are just lists of files. I doubt your files are corrupted (unless something is corrupting data in general; e.g. a failing HDD), but if the collection files seem to have random data in them then that could be related to the problem you're seeing.
Please zip up /dopusdata/Collections and include those with the crash dumps so we can take a look at them.
(/dopusdata usually maps to C:\Users<Your Name>\AppData\Roaming\GPSoftware\Directory Opus.)
Is anything unusual being done with the collections, e.g. running lots of automated Find tasks, or importing them from an external tool? (e.g. Everything, or a custom importer via dopusrt.exe?)
I dont think im doing anything unusual with the collections but maybe im wrong. This probably has nothing to do with it but I do add brackets to my filenames & i have noticed when i try to filter filename in flatview it doesnt work if filter includes a bracket.
On another note. Im using an older version of Dopus i paid for but my email wasnt even in your system anymore, where i still have the confirmation email in my inbox.
heres a screenshot of the collection.
I'm uploading the dump files now.
Brackets are wildcard characters. If you want to search for a literal bracket in a wildcard use '( instead of ( on its own. The single quote ' escapes the character after it,
The account could have had its address changed, or you may have a newer code than the one you're using to log in. I think only the most recent code would work. Please contact sales@gpsoft.com.au if you need to troubleshoot Opus registration / gpsoft.com.au account details, and let them know the details you're using. (Don't post them here, though.)
thank you.
I just emailed my dumps.
I didn't realise we were talking about Opus 9.5.6.0 from 2010.
The dump files are of limited use in that case, as we don't keep debug information for versions that old (there wouldn't be much point, as any observations would be unlikely to apply to the current codebase).
We could still try to look at the collection with the corrupt filenames, but it seems to be missing from the zip we were emailed. The screenshot shows a collection below coll://-opened-/ called 2017-05Feb-France Shield Fleur, but no such folder or file exists in the zip. Looking at the folder tree in the screenshot from the zip, there are a lot of collections which aren't in there.
If you have a huge number of collections (hundreds/thousands), that did cause Opus 9 to become very slow, and was improved in later versions (it looks like in one of the early Opus 10 updates, from some quick research into the archives). So you may find that deleting unused collections speeds things up, and/or updating to a newer version makes that problem go away. (Note that Opus 9 was released before the version of Windows you're using as well, and isn't officially supported on it. It's a very old version now.)
