If Defraggler is left open for an extended period of time -- For instance, if it's defragging a large drive, or if you simply minimize it -- It tends to use up huge amounts of RAM. This is just a quick example, however i've seen it hit 700MB+
I brought this up in 2008, in Windows XP. The issue has persisted over the year, through Vista, and now Windows 7... Would be nice if this got sorted already.
It wouldn't surprise me if any active program would try to use as much memory space as it needs, if nothing else is running. Surely that's the way Windows memory allocation/optimisation is supposed to work?
The exact instant i open Defraggler, it uses about 90MB of RAM, but that's only with one HDD visible.
As more HDD's load into the list, Defraggler jumps to exactly 299MB RAM usage.
If i re-open Defraggler, it doesn't reload the list of hard drives, but it instantly uses 299MB of RAM.
Computer specs:
Intel Q9550 CPU
ASUS P5E motherboard
GTX285
8GB DDR2-800MHz
4 HDD's
- 2x400GB RAID0 (3 partitions)
- 2x1000GB regular
- Shutdown your PC
- Disconnect a drive from each Raid Array & reboot, try it again.
- If this solves the problem, check the switches for correct Master/Slave setup on the drives themselves.
- If this doesn't solve the problem, connect the drives (1 drive, non raid array) directly to the MoBo instead of a Raid Card & see if that solves the problem.
- If this still doesn't solve the problem, try connecting a flash drive or some other drive & see what it does without the other drives installed/running.
I run RAID0, i can't disconnect a drive without destroying my array.
Besides, why the hell would i want to do that? If MyDefrag, Auslogics Defrag, PerfectDisk, O&O Defrag, Diskeeper, and many more defragging programs run without any problems (excess ram usage), why should Defraggler be the exception?
Furthermore, when i had Windows XP, i didn't have a RAID array.
I don't think drastically changing my hardware setup is the right thing to do, considering Defraggler is the only program that suffers from this issue.
I don't think drastically changing my hardware setup is the right thing to do, considering Defraggler is the only program that suffers from this issue.
I'm with him on that one.
I'm also seeing the same problem, and can confirm that the more drives you have the MUCH more memory defraggler uses.
I'm sure there's some design flaw in the code somewhere that misappropriates memory/forgets to release it.
Uses 230? MB on my 4-HDD xp64 system. I have 8 GB of RAM total.
Other big users include K-Meleon and AVG.
I don't have any problem with Defraggler's memory demands, as I would expect a defrag app to take a lot. Other defraggers I've used were more intrusive than Defraggler (especially OO) and, to me, Defraggler seems light and quick. (I wish I could say the same for Nero, which I like but which is really demanding and sensitive on my box.)
I agree that programs such as defraggers will serve best by using lots of memory if it is available. You want scans like this to work fast. If the system were crashing or seizing up because the memory usage were crippling it, THEN I would be concerned. On my box, Defrag completes the defrag of any selected drive and then Task Man drops Defraggler from the chart altogether, so I'm assuming that means that Defraggler has quit upon finishing and is now consuming nada.
It's a memory leak... It doesn't affect your defrag times or stability. It's simply an issue caused by the number of drives listed.
It's a bug.
Well, my Defraggler memory usage has stayed fairly constant at 361,024 KB (give or take a MB or so) for about half an hour while defragging.
Memory leaks cause the amount of memory used to increase with time, and (some of) the memory is not returned to the memory pool when the leaky program terminates. Is this what you observe?
I have Paragon Drive Backup is an exact copy (sector to sector, the same) in my partition "Z" made (65914 files, 32.6 GiB of 150GiB, 20% fragmented) and this once again with one competitors and their exact copy with Defraggler, defrag on the same partition.
The result:
The competition took 34 minutes and Defraggler took over 4 hours!
I repeat that again. The same result ... But why Defraggler takes so long?
Not sure how to post debug information from Defraggler.
Care to explain?
Also the latest version of defraggler with the changelog "- Rearchitected memory management on Vista/W7." still has not made a difference to the memory usage. In fact, it increased slightly.
