Ever since upgrading to the v13, DOpus hangs all the time. It hangs when opening, when opening some directories, when highlighting, etc. It's constant and doesn't seem to have a specific trigger that I can find. It's so bad that I'm about ready to uninstall DOpus because it's nearly unusable. Just opening into a director can take up to a minute, which DOpus is "not responding."
I keep my Windows updated and all drivers updated.
Is there a way to downgrade and get my upgrade price back? This is the worst Dopus has every worked for the many years I've used it.
I also sent an e-mail to support, with no reply in weeks.
Please send us some process snapshots made while the freeze is happening. We can usually look at those to see what the cause is.
(Tech support questions should be posted here. The sales@ and info@ email addresses are only for sales questions, since the rest of the team doesn't see that inbox.)
Thank you. The snapshots don't show anything unusual, unfortunately.
Were they made while the freeze was happening? It looks like Opus had just been launched when they were made.
Is it just one window that's freezing or the whole program? Does opening a new window work or does that also fail?
Does the freeze happen by itself if you just launch Opus and do nothing, or does it happen in reaction to a particular action, or going to a particular folder (or viewing a particular file, etc.)?
The issue with the log dumps is the freeze happens, but by the time I can create the dumps, it un-freezes. Freezing happens sometimes for a few seconds, and sometimes for up to a minute. It's random. Sometimes it doesn't freeze at all no matter what I do. Then next time it will freeze upon opening DOpus and trying to use it. Sometimes the freezing is just not updating the listing (I sort by modified, for example, and nothing happens. DOpus doesn't show "not responding" or anything, but the listing doesn't change/sort for up to a minute.) Other times, DOpus doesn't respond and turns all white. I wait for a while and it resumes. Other times I can't move the window. It's stuck or not responding. Again, wait a bit and it resumes and works.
I have no issues with other windows and I didn't have this issue prior to v13 that I recall at all. But it's common now.
Try a sys check on your system . That will check if there is problems with your system files. Also do a check disk check to see if there is a fault there.
That sounds like something is pointing at a network drive which isn’t on the network.
Look for shortcuts, toolbar buttons (including their icons if they point to things on the network), favorites and anything else that might be pointing to a network drive.
I do have a network drive, but this has never been an issue. There is certainly a delay when accessing a network drive if it's idle, but that's normal.
I have a second machine on my desk that uses the old DOpus and same network/setup. I don't have these freezes. Both access the same network drive.
It could be the issue now. Something has changed somewhere.
It could also be another network path somewhere in the toolbars/favorites/etc. that's being accessed and has to time out before it fails. (Windows will block network filesystem access for up to 30 seconds waiting for a non-existent server to respond.)
You could also try using Process Monitor to see if it shows which path is being accessed around the time the delay happens.
Or see if you can generate some process snapshots while the delay is happening.
Is the problem present with all drives or only with external usb drives?
are the usb drives connected via a hub?
have a similar problem with a complete system crash under windows 10
must have been added as a bug at some point in a 13 version.
this does not occur with the 12.
the 12 (portable) is only used as a back-up test when a problem occurs.
several tests with other software/hardware have shown that it is actually due to the 13.
With do13 external usb activities cause the entire system to crash.
With do12 this ran for several hours with the same activity without any problems.
a topic with more detailed information is in progress.
(may take some time)
I use a DO13 on Win 10 everyday for work, with regular use of USB devices : no system crash to report.
I tend to think like @lxp that it is unlikely linked to DO13. The problem might be eleswhere.
A user-mode program like Opus can't cause a whole system crash. There's something caused by something lower level, like drivers or hardware or things that intercept them like antivirus.
Opus 12 and 13 (by default) copy files in different ways, which may be why one didn't trigger the problem and the other did, maybe, but the problem isn't actually in Opus. And the way Opus 13 copies files by default is the same as how File Explorer does.
are 2 to 4 end devices (3.5” drives) connected to the system at the same time,
either directly or via a hub (with power)?
individual small/large files work
but unfortunately many large ones do not.
the long running time during operation seems to be the cause.
the test was also carried out there.
the system was also stable here.
could perhaps have something to do with the change in the transmission type!
explorer/dopus12:
copy/move between 2 nas
nas -> windows -> nas = 52mb/sec.
copy/move between nas and external usb
nas -> windows -> usb = 68mb/sec.
dopus13:
copy/move between 2 nas
nas -> nas = 110mb/sec.
copy/move between nas and external usb
nas -> usb = 140mb/sec.
this probably seems to overload the system!
I also use Opus 13 with multiple USB devices connected, and I also use NAS. I never had the problem of total crashes either.
@ScottHMcCoy it may be worth trying to first backup your current Opus configuration, and then reset it to default values (the option is in the same window).
If you notice that the problem has disappeared, then that suggests that the issue lies somewhere in your Opus settings.