I currently use version 11.19 x64 on Windows 10.
It has been the case in the past when using Windows 7 and 8.1 that opening a folder containing .cvx files produced in ACD Canvas would produce a slow response from Dopus, before the lister was populated. This has continued into Windows 10 with the added nuisance that the program often crashes and invites me to terminate the thread, then closes. Mostly it will work properly on restarting.
It's not a major problem, but it would be good to be rid of it.
Does File Explorer have a similar problem?
If any crash dumps were generated, please send them to us so we can investigate. The problem is likely to be in a 3rd party component (probably something involved in that file format), but we can use the crash dumps to confirm that. It's always possible something in Opus is going wrong as well.
See also: Crash, exit or high CPU usage when viewing certain directories
Thanks for sending the crash dumps.
The crash is happening when display the icon for one of the files in the folder. It's possible this is due to a shell extension providing invalid icon data or corrupting memory when asked for an icon, but that's just a guess at this stage.
From here, there are a few things to try:
-
Turning on Preferences / Folders / Folder Display / Show generic icons for... the type of drive the files are on should prevent the crash, if it is due to icons. That's a good, quick test to check we're on the right track.
-
Using ShellExView, sort the list of shell extensions by Type, then select all the ones with Type Icon Handler and Icon Overlay Handler, then right-click them and disable them. Reboot afterwards, and see if the problem still happens, with Show generic icons for... set back how it was originally.
If that makes the problem go away, re-enable a few at a time until it comes back, and you should be able to work out which one is causing it.
-
If possible, it might be worth trying with Opus 12 in case it's something we've already made a fix or workaround for. There have been some changes to avoid problems caused by shell extensions providing invalid icon data, most of which were also in Opus 11 but it's possible there are some newer ones only in 12. That said, I don't think any involved crashes, only blank icons, but it's possible something has changed to cause the invalid icon data some shell extensions return to have a worse result than before.
-
The crash dumps also have something which we've seen in other crash dumps that were caused by a bug in Windows 10 itself, and the way it collects telemetry about everything that runs on the system. We've only seen this cause problems with Windows Insider builds, not normal Windows versions, but the pattern is definitely there, so it might be wroth ruling out. (It's also entirely possible it's unrelated and unimportant, but we don't know until we try.) The Windows telemetry service that has caused some people problems can be disabled as follows:
-
Press Windows+R (or Start -> Run) and enter services.msc to open the Services control panel.
-
Locate the Connected User Experiences and Telemetry service, select it, and click the stop button at the top of the window to stop the service.
(note that if Opus is running, it will probably crash immediately at this point) -
Right-click the same service entry, select Properties from the context menu, and change the Startup type to Disabled. Click OK.
-
Restart your machine