Search results

Re: A couple of Eraser problems! It's a pity that I can't now reproduce the problem. I would send you the full dump of memory when Eraser 6.0.8 occupied more than 7Gb of memory!

Re: Eraser 6.0.8.2273 occupied a lot of memory while wiping. At first were 17 threads, but some time later there were only 13 threads. Eraser 6.1.0.2284 also worked and finished the tasks but it used more memory with option "the Force locked files to be unlocked for erasure". One question...

Re: Eraser 6.0.8.2273 occupied a lot of memory while wiping. It is strangely! After I have reinstalled .NET 3.5.1 Eraser 6.0.8.2273 can't run - Windows close it. Deleting and new install could not solve the problem. So I installed Eraser 6.1.0.2284 and it works. Next I turn off the option...

Re: Eraser 6.0.8.2273 occupied a lot of memory while wiping. Just a minute...

Re: Eraser 6.0.8.2273 occupied a lot of memory while wiping. Joel, may be so much memory allocation occurs because of wrong .NET installation and that's why garbage collector can't work properly, but all the same Eraser occupies a lot of memory even it works properly! Can you answer me why you...

Re: Eraser 6.0.8.2273 occupied a lot of memory while wiping. My comes with 4.0 :) There is no any .NET Frameworks in <Programs and Features> except for .NET 4.0. There is a checkbox for .NET 3.5 in Windows Components and it is checked. For Windows 7 .NET 4.0 is default.

Re: Eraser 6.0.8.2273 occupied a lot of memory while wiping. I just tried to install .NET Framework 3.5 SP1 on my Windows 7 x64. It could not install, begins and then close the setup program automatically. In dotNet35SP1Readme.htm there is info: So, there is no support for Windows 7...

Re: Eraser 6.0.8.2273 occupied a lot of memory while wiping. This is too much! Do you disagree, David? Why it needs so much memory and this is without erase cluster tips. Why it can't erase clusters tips direct with no-buffering IO? What .NET Framework version I must install manually? I'll...

Re: Eraser 6.0.8.2273 occupied a lot of memory while wiping. I still have problems, have done the above you wrote. 1. Wiping file. All is ok. 2. Wiping free disk space without erase cluster tips on disk 1. Total memory occupied more than 1GB! It begins not at once and rises gradually...

Re: Eraser 6.0.8.2273 occupied a lot of memory while wiping. I have a bad news(for me). I ran the task to wipe unused space without "erase cluster tips" option and I get the same result! Eraser took a lot of memory and I got "out of resources".

Re: Eraser 6.0.8.2273 occupied a lot of memory while wiping. May be next code helps to solve the problem? GC::Collect(); GC::WaitForPendingFinalizers () ; How I can say it to the developers of "Eraser"?

Re: Eraser 6.0.8.2273 occupied a lot of memory while wiping. But if I need to erase cluster tips how can I set up .NET Framework that it worked properly and garbage collection could work properly?

Re: Eraser 6.0.8.2273 occupied a lot of memory while wiping. What can I do to finish my tasks "wipe unused disk space"? What Framework version does Eraser use(compiled with)? Is it 2.0?

Re: Eraser 6.0.8.2273 occupied a lot of memory while wiping. To my mind there is a leak of memory in code...

Eraser 6.0.8.2273 occupied a lot of memory while wiping unused space of hard disk! And windows close it, that's why it could not finish the task . 6 385 144 Kb of Virtual Memory and 3 165 452 Kb of Physical Memory!