Hi, I've noticed that during some file copy opus 10 caused svchost to hog an huge memory amount... The same operation does not causes that, using windows 7 file explorer. I read that since beta 10.0.0.1 a similar problem stated to be fixed, but it seems it's not... please look at this:
then after a while:
and further more:
any idea?
thanks...
Important edit: Just after the post I' ve noticed that all the memory is taken up during large files copy (see the screens: e.g. 7 giga), but it's released when going to copy some smaller files (in the same queue). So, I don't know if it's normal, but it's seems a bit strange that before DO finish to copy a 7GB file, it needs to use ~500MB of RAM...
Sounds like it's something one of your hardware drivers is doing (Opus doesn't install any services itself). If the memory is released at some point then it's not a leak but maybe it indicates the driver is caching file data.
Turn on the command-line column in Task Manager so you can see which service scvhost.exe is hosting there.
Changes are if you then look for articles about that service using excessive memory they'll point to a hotfix or setting that will make it stop happening.
Sorry: the last post was wrong and misleading: THE PROBLEM IS PRESENT (I unchecked by mistake in task manager de checkbox to show svchost.exe processes, so I thought the memory was released. It is not.)
Notice the 630MB used by svchost... the memory leak suddenly stop as soon I cancel the DO copy dialog, but memory is NOT released at all.
Please notcie: the problem it's not happening if I copy the same files using Win7 explorer.
You'll need to find out what service it is by doing what Leo suggested.
Ok, I did: the command line is: "C:\Windows\System32\svchost.exe -k LocalSystemNetworkRestricted". What should I see from that...?
Thank you.
Try going to the Services control panel and stopping the Superfetch service and the Indexing service.
Sorry, not Indexing service, the Windows Search service. (At least on Win7. Maybe it was Indexing service in the past.)
Anyway, the Superfetch and Windows Search services. Try stopping them.
Try the Windows Defender service as well.
(Once you're done, you can start them again or just reboot to get things back to normal.)
Also check if there is an upgrade available for your network drivers.
I cannot thank you enough: as soon I stop the "superfetch" service, all the memory taken up from that svchost instance is immediately released! Than if I try to copy somee files, the problem is disappeared. As soon I restart the service, ~80 MB RAM is taken, and the bug upon copy reappears.
Now: I thought that superfetch was usefult to optimize the system startup. But why this issue happens. Should I disable it? It is safe?
Another thing: as I said, the problem does NOT happend using standard file explorer... I don't know why, but it is so.
I'm not sure why you're worrying about this. If the memory is being used by superfetch as a data cache, it will still be available for your programs to use if needed. What's the point in having your RAM sitting there unused?
I'm worried because after 7 GB copied from a disk to another I have 500+ GB RAM used and when the copy finished, the RAM is not released. I think that without rebooting the PC the RAM could be used to the limit. And I'm worried because the program that I love seems to cause this; explorer does not... 
anyway thank you for your time guys, hope if there's a problem with DO it will be found and solved... I'll try to leave superfetch up and running, because I think that is a good thing anyway...
The memory will be released by the caching system if it's needed for anything else. Have you ever actually seen an 'out of memory' error?
No... in fact I hope you're right. I'll take it easy until any error will be shown 
thank you by now
Superfetch goes crazy sometimes, especially in Vista (much rarer in Windows 7).
I ended up completely disabling it on some machines when they had Vista as it decided that a file was really important, because it had been accessed a lot, and had to be cached at all times. Problem was the file was larger than the amount of memory the machine had, so Superfetch was constantly reading the start of the file in, which pushed the end of it out of memory, then reading the end in, which pushed the start out, repeat forever. HDD never stopped accessing, which wasn't great on a laptop.