Runaway memory usage when Check Disk in Windows7 64bit

Help & Support
1

Dopus version 9.5.4.3806x64 has a runaway memory usage problem under Windows7 Ultimate x64.

Specifically:

  1. Right-click any local hard disk drive and select properties.
  2. Click the Tools tab and choose Check Now...
  3. Check both boxes in the Check Disk Options window and then click Start.
  4. A few seconds after the process starts, click the Cancel button in the Check disk options window to stop the scan.
  5. At this point the scan will continue in the background, and opening Task Manager and clicking on the Processes tab will reveal that Dopus.exe is gobbling up system memory with alacrity...a process which will continue even after nearly all the physical memory has been allocated to Dopus.exe.
  6. Making certain that all Disk Check windows are closed out will still not stop this runaway process.
  7. One can end this havoc either by manually ending the process (dopus.exe) in Task Manager, or by right-clicking the Dopus icon in the notification area and selecting Exit.
  8. Not sure if it's normal, but whilst this is going on, if access is attempted on the drive with another lister, the error, "An Error Occurred Reading Folder, Access is Denied. (5)" And this after all drive check windows have been closed.
2

Now try exactly the same thing in Explorer and report back.

3

Are you sure it's Opus using up the memory?

When I do the same thing, dllhost.exe (not dopus.exe) is what uses up the memory. That is a by-design feature of Windows and you can find blog posts on the web explaining why they made the check-disk feature use as much memory as was available (and why it shouldn't be a problem).

4

Perhaps this is, after all, normal behavior...however, it is the dopus.exe process (at least, on my machine) which uses nearly all of my system's 8GB of memory.

5

And if you do the same thing in Explorer?

6

Jon,

You're not a lawyer, are you (one who knows the answer to a question before posing it)?

Of course, explorer.exe is the process which grabs the memory if Dopus' "replace Explorer" is disabled.

Yet I still find it odd that this continues after cancellation of the task...perhaps until the background process completes, even when one has ordered it not to.

Dopus is off the hook, then, right?