Jump to content
CCleaner Community Forums


Experienced Members
  • Content count

  • Joined

  • Last visited

Posts posted by Willy2

  1. - Makes perfect sense. Because Windows needs to keep track what has been changed (files, etc.) and put that in the (next) System Restore Point. All that info allows Windows to revert the changes that have been made when one installs a program or an app.

    - Question: did the amount of free disk space shrink as a result of using Defraggler ? People have been complaining about that in the past.

  2. - Piriform issued a new version of DF (v2.22). Instead of adding a "Privacy" tab (in the "Options" menu) the developers should have focussed on fixing a number of other things/bugs as reported in this thread.

    - What hasn't been fixed and what "annoys" (to put it friendly) me the most currently is that DF is the following: When the user has chosen to store the DF settings in a *.ini file then DF doesn't store all (???) the changes the user made in the *.ini file. To make sure that these changes are properly recorded/stored I have to (manually) edit that Defraggler.ini file. Grrrrrrrrrrrrrr.............

  3. - Re-installed DF v2.22 today and the program still "doesn't get it". Although I switched the language (to dutch), DF didn't translate 2 text strings in the main screen of the installation program. They remained in english. Did the translator forget to translate these strings ? Bug in the program code ?

    - This wasn't related to e.g. a missing *.ini file because I removed all DF related info.

  4. -  Install PcWinTech's CLEANMEM. Then there's no need to reboot your system to get memory usage lower. Because it runs every 15 minutes using Task Scheduler and then reduces memory usage. The program uses an API that's build into Windows itself (Windows XP and newer).

  5. - "BlackViper" has some sound advice regarding the amount of memory (although it's from the year 2008).


    - My personal opinion is that one only should start (!!!) to worry about memory usage when the "In Use" part of the memory is and remains above say 70% to say 80% of total memory for a (very) long time.

    - If even installing CLEANMEM (see above) doesn't help to keep memory usage much lower (under say 70% to 80% of total memory), then and only then I would start to consider buying more memory.

  6. I must add some more comment to my previous post.

    - When the user executes steps 1) through 5) (see previous post) then the GUI reverts back to (what seems to be) the default size of the GUI right after a fresh new installation.

    - But CC does remember what boxes were ticked when the user closes CC with the "Exit" option (in the menu of the system tray icon).

  7. @ Nergal:

    - I was in doubt whether or not I could use the name of the program. I decided to have a go at it. Especially because it provided guidance on why that file became so large. It was meant to provide as much details as  possible.

    - Did I ask for a solution ? I told what the (special) circumstances were when the video started to stutter. And gave my thoughts and a number of suggestions.

    - In a previous post in this thread "Stephen Piriform" asked me to provide more details of my system and that's why I attached that info/file to my previous post. NOT because I was so desparate for a solution. Because I already knew what the problem was, why the video didn't behave so well.

    - In my experience, exceptional circumstances (like this one) always shed a better light on how a program behaves. And this special combination of circumstances certainly provided - IMO - some (VERY) useful clues, precisely because they were so exceptional. And it's up to the CC developers whether or not they want to use my suggestions to improve the program code. Whether or not they find thse suggestions useful.

  8. - I found out what the reason is of the stuttering video. While watching a video I started CC. But when CC starts it reads and processes the file "Winapp.ini". That file is on my system over 700 kb in size (made by "Voldermort").Then it takes CC "more than a few seconds" to process that file. At the same time CPU of CC goes "through the roof" of one of my 4 CPU cores (I have a i5 Intel CPU, see my signature).

    - The odd thing is that, with the monitoring feature enabled, there are 2 processes called "Ccleaner.exe" and CPU of BOTH CC processes "go through the roof" (a second CPU core, see Task Manager) together, when "Winapp.ini" is being processed. Seems that the process controlling the monitoring process is somehow intertwined with the other CC process and has more difficulty of doing its job as well.

    - When "Winapp.ini" has been processed CPU of both CC processes go down to (almost) zero.

    - I also noticed that - from time to time - my webbrowser can push CPU usage to (very) high levels. When these things happen at the same time (browser, starting CC and watching a video) then it's no surprise to see CPU go through  the roof and a video that starts to stutter (more than) a bit.


    Came up with more suggestions:

    1)  Isn't it possible to re-write the program code that processes the file "Winapp.ini" to avoid high CPU readings for the process "CCleaner.exe" ? Doesn't the CC program code remember at what place/point it was when it had checked each line in the file "Winapp.ini" ? Does CC start to read the file  "Winapp.ini" from the beginning of the file, each time it has processed one line in "Winapp.ini" ? If so, then I think that re-writing the program code could (dramatically) reduce the time needed for processing "Winapp.ini".

    2) Let the "monitoring" feature remain idle until CC has finished processing the file "Winapp.ini". I think this way CC can avoid high CPU usage of the "monitoring" part of the program code. This could be combined with a delay of say 2 to say 4 minutes before starting the process.

    (Although this particular situation was an exception, it did provide some good clues on what the logic is inside the CC program code and could provide the developers of CC some insightful clues on how a future version of the program can  be improved).

    (I also attached the file procduced by "Run DxDiag", as requested in a previous post in this thread)


  9. - Install PcWinTech's CLEANMEM.


    - The program reduces the amount of "In Use" memory and pushes that to the "Standby" part of the memory. Then the regular memory  management will be forced to make decisions on what to do next. The program will also reduce the impact of memory leaks.

    - The program also can collapse the file cache. I have come across a filecache of GBs and then that DOES turn one's system into a snail with heavy disk I/O.

  10. - System setup: See my signature !!!!

    - I will report back with more info. Your reply gave me some clues

    - Suggestions:

    1) Make sure that this monitoring feature runs with a (much) lower priority.

    2) CC can be set up to run upon start up. But I also know that Windows performs A LOT OF disk I/O in the first say 2 to 5 minutes after the user starts his/her computer. That could interfere with CC. Perhaps Piriform can build in a "start up delay" of anything between say 2, 3, 4 or say 5 minutes ? (I know 2 programs that have such a "start up delay").