The guide says: "Use the standard Task Manager to keep an eye on dopus.exe's memory usage so you can tell when you've triggered the leak." When I run dopus.exe through VMMap.exe, the process that is holding all of the RAM, sometimes 12GB or more, isn't dopus.exe. It's VMMap.exe. In any case, when I look at the trace and stack, what I see isn't any other application running on my computer - its dopuslib.dll.
In any case, this problem is solved!
I have DO running on the affected machine (my laptop) and on another system (my desktop). The desktop doesn't exhibit the behavior and memory levels are normal. The two computers are both running Windows 8.1 and I have the same applications installed and running on both systems. I' was going to look at what is different between them to see if I could find the offending program. As the laptop is an HP system, with the attendant HP utilities running, I was starting to suspect one of these utilities.
Before I could start on that, though, I was struck by another possibility - that it had something to do with 32-bit memory mapping. I don't know much about this, but as I mentioned in an earlier post, the top process in the VMMap.exe trace after I'd captured data with the leak was VirtualProtextEx. This was always a byte size of 65594. I tried an experiment and loaded VMware Workstation and started a Windows 8.1 virtual machine. Workstation started fine and loaded the VM, but when it actually tried to start it, I got an error message that the virtualization setting in the BIOS wasn't turned on. I remembered that a couple of weeks ago, my HP utility software notified me that there was a BIOS update. I approved the installation, the system rebooted, and everything worked fine. Today, I rebooted to double checked this, and discovered that the BIOS update apparently had disabled it. When I reenabled it and restarted the system, the DOpus problem was gone. I've been running Opus for several hours with no memory issues. Unless something comes up, I guess this is fixed.
So, the moral here, for anyone experiencing an apparent memory drain by Opus, is - check your BIOS settings and be SURE that the Virtualization Technology or 64-bit Virtualization or whatever your particular system calls this feature, is ENABLED!
Thanks to Jon and everyone else who assisted me on this. I didn't realize until the last few days of wrestling with this, how much I depend on Directory Opus. Having to shut it down every time I wasn't using it was not only irritating, but seriously impacted my work flow.