Jump to content
CCleaner Community Forums

Defraggler: Willy2's bug reports


Recommended Posts

I noticed that the developers of Defraggler (DF) are planning a new version of the program. Well, then they only have to read this thread to see all the things that can be improved/fixed. And as they can see, I have come across A LOT OF things that can be fixed and improved.

Some of the bugs in this thread are clear and obvious bugs that need to be fixed and can be (easily (??)) fixed. But other bugs don't show a reliable pattern of when and where these bugs are occurring. In those cases I think this "irregular" behaviour can be fixed by, what I would call, "better protecting the internal DF variables" and/or improving the memorymanagement.

If I was asked to give a list of the fixes/improvements that have for me the highest priority then it would look like this:

1) Fix the multiple issues/bugs in the "Move files to end of drive" options which prevents the program from properly moving the all right files. See the 2 red arrows in the 1st picture.
2) Improve the "move to the end of drive" subroutines. In the 2nd picture I have an example. Here DF moved a number of files (blue boxes + red arrows) to the end of the drive. But after moving the files there are still (large) gaps (black line & black arrow).
3) Improve the "display blocks" routines. When I click on every empty box between 2 groups of blue boxes (above the black line) then DF reported that there were still some 4 or 5 files in that gap (above black line) but not all these files showed up in the file map between the files.
4) (Sharply) Reduce the time the program needs to stop. The user can decide to interrupt the program when the program is performing some operation (e.g. moving files to the end of a drive). But then it can take a LONG LONG time (up to 5 (10 ??) minutes !!) before the DF program code has really finished "stopping". The sign that DF is still (very) "busy" doing something mysterious, is the (very) high CPU as shown in Task Manager. And when I am really fed up, I simply use Task Manager to abort the DF process.

Screenshot_25.png

Defraggler1.png

System setup: http://speccy.piriform.com/results/gcNzIPEjEb0B2khOOBVCHPc

 

A discussion always stimulates the braincells !!!

Link to post
Share on other sites
  • 1 month later...

- Have run Defraggler to move a bunch of files towards the end of the C: drive. I was astonished to see that, after having finished the job, the program kept running with a very high CPU for about 50 (!!!!) minutes. I know that it can take DF a considerable amount of time to "wind down" but ~ 50 minutes is ridiculous, outrageous.

System setup: http://speccy.piriform.com/results/gcNzIPEjEb0B2khOOBVCHPc

 

A discussion always stimulates the braincells !!!

Link to post
Share on other sites

- I want to post a follow up on my post dated November 21, 2020.

- It seems - I repeat - SEEMS (!!!) that when the user sorts the search results on "Fragments" that then the program code acts as if the user want to sort the search results on "Last Modified". In this regard "Fragments" doesn't sort on "fragments" at all !!!

- The program code could contain a "Sort on fragments" sub-routine but then it seems this "sort on fragments" program code isn't used at all.

- The good folks at CCleaner should examine the "Sort on Fragments" program code in detail to see what's REALLY going on when the user want to sort the search result on "fragments". I can't make head or tails of it. But it simply doesn't work.

System setup: http://speccy.piriform.com/results/gcNzIPEjEb0B2khOOBVCHPc

 

A discussion always stimulates the braincells !!!

Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...