After six years with Opus I'm trying out collections. I'm using W7 x64 with 10.0.0.4. Either when clicking on file collections in tree, making a new collection, or adding a files to a collection DO abruptly crashes with the "stopping working" message. It's never let me do more than 10 seconds of work it a collection. Process Monitor doesn't show anything exceptional, and no dopus.minidumbs are created.
Any other ideas in terms of tracking down the issue?
[ul][li]Make a note of where /dopusdata/Collections points to in Opus, and open that location using Windows Explorer.[/li]
[li]Exit Opus (use the jump-list or File -> Exit Directory Opus; don't just close all the windows).[/li]
[li]In Explorer, rename the Collections folder to something else.[/li]
[li]Re-start Opus and see if things work again. If they do, zip up the old Collections folder and we'll take a look at it.[/li][/ul]
When I rename the collection folder, launching Opus re-creates the physical collection folder. The results are the same, sometimes it crashes just because it clicked on collections, other times I can add a few files or folders before it bombs. I'll try a repair and a full reinstall when I get a chance.
Re-installing on top of DO had no effect. After an un-install and re-install, collections work until I restore misc data. Any idea on where to start troubleshooting?
So we know it's triggered by something in your configuration, which is good. (Well, better than not having any idea what's causing it. )
If you want to send the config backup to me via a PM I will see if I can reproduce the problem after importing it.
If you don't want to send the config, I think the quickest way to find the trigger it is to revert to a default config and then restore individual directories from the config backup until you find out which one causes the crash. Then isolate which file within that directory causes the crash. When doing that, Opus should be exited before the config is changed (since exiting Opus may flush config files from memory to disk, overwriting manual changes you had made).
Config backups are really zip files, so you can rename their extensions to look inside them.
I think we have found the problem and a fix has been written for the next version.
For the time being, I think you can avoid the crash if you edit your Collections folder format and ensure it does not have any columns like Description, Width, Height, etc. which cause file information to be extracted/calculated. (Basic info like size and date is fine.)
That does seem to have fixed it. I have description invoked in my custom default format. Removing description and invoking the collection default format seems to have fixed the issue.