Jump to content

Willy2

Experienced Members
  • Posts

    1,829
  • Joined

  • Last visited

Posts posted by Willy2

  1. - 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.............

  2. - 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.

  3. -  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).

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

    http://www.blackviper.com/2008/03/04/how-much-memory-do-i-need-for-my-computer-what-is-the-maximum-supported-for-my-particular-os/

    - 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.

  5. 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).

  6. @ 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.

  7. - 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)

    DxDiag.txt

  8. - Install PcWinTech's CLEANMEM.

    http://www.pcwintech.com/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.

  9. - More odd behaviour in CC v5.46.

    Took the following steps:

    1) Opened CC (switched to english and checked the "Save settings to INI file" and the  "Enable  monitoring" boxes.)

    2) Maximized the CC GUI.

    3) Closed the main CC GUI.

    4) Closed the  CC tray icon.

    5) Re-opened CC but now the CC GUI reverted to a much smaller size.

  10. - I know, I know. Don't worry:  No offense taken.

    - Another suggestion: Perhaps start both the "monitoring feature" and the CC "automatic cleanup" program code upon start up but let them wait for say 2, 4 or 6 minutes before the CC program code allows these features to come to live.

  11. - 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").

     

  12. - I see another reason why a user would want to turn off the "Monitoring" feature. If one's computer is busy with a task that requires a lot of CPU power then every extra (CPU consuming) task (e.g. CC "monitoring" one's HD) can lead to an overall slowdown of one's system.

    - I was watching a video and during that process I started CC. And I noticed that the video (player) started to stutter. As soon as I closed down CC and the CC monitoring feature, the stutter (in the video) was gone. Perhaps some other process was also using a lot of CPU but nonetheless, I found the difference to be remarkable. It was simply one task too many for the CPU.

  13. Two more language related bugs in CC v5.46:

    1) Installation program:

    - I switched the language to german and also checked the box "Save settings to INI file" in CC. Then ran the CC installation program and the texts in the installation program were all in .......... english.

    - After unchecking the "Save settings to INI file" I ran the installation program again and now all texts showed up in german. This means that the CC installation program checks the registry but not the INI file (I always use the default installation folder).

    - It reminded me of what happens when the user has checked the same "Save settings to INI file" box in Defraggler. Then that program also goes (a bit) "off the rails".

    - I also noticed that - in this case - the main CC program fails to look whether or not there's an INI file. Because when I opened CC it started with the default options/boxes checked. Perhaps the INI file must be read at a (much) earlier stage in the program code ?

    2) "Smart Monitoring" feature:  When this option has been enabled CC (after performing the steps under 1)) after a while a window shows up with the message that the program has found files that can be deleted. But this window showed up with both english & german texts.

    Conclusion: CC has some (severe ??) problems when it comes to handling the INI file.

  14. Update:

    - System Tray Icon: It seems that the 1st time, after installation, the icon shows up with the tooltip in the selected language (For me that's dutch). But when I start the program (CC v5.46) for a 2nd, 3rd, 4th, 5th, ....... time the language (seems to) revert(s) back to english.

    - I used the "regular" version downloaded from the Piriform website.

    - This is odd, very odd. I repeated the things I have reported before (monday, september 3 (@ 14.01) 2018). And now all seems to be well. And no, I didn't "lose my marbles". Is there here interference from some other program ?

    - What I saw is that the installation program looks what language version the user has selected for an older\previous version and then displays the texts in the installation program in that language.

  15. - Another language related bug in CC v5.46: When I change the language to dutch then CC forgets to translate something. The language of the CC system tray icon remains english. Instead of displaying a dutch text, an english text shows up ("CCleaner Smart Cleaning is enabled"), when I place the mouse cursor over that system tray icon. Keep in mind this is AFTER a restart of my system !!!!

    - Bug in the program code ? Translator having a "bad hair day" ?

  16. - Alas. Support for IMAP is still something for the (near ??) future. The developers wrote that IMAP already works on their servers. But that's all they are willing to say. Perhaps they still need to get rid of (A LOT OF) IMAP related bugs in the OEC program code. I don't know what's going on.

    - The PRO version allows the user to separate emails in separate "Identities". I.e. you can separate e.g. your private emails from e.g. your work related emails.

    https://www.oeclassic.com/online-help-identities

    https://www.oeclassic.com/online-help-quickstart

    - OEC seems to work on Windows 2000 and newer.

  17. - Just a few minutes ago I installed (in the following sequence, I still have all three versions) CC v5.45, v5.44 and then v5.46. And it seems (!!!) that all programs have the same problem. The installation part of the program recognizes that I have a dutch system but in CC the GUI itself the texts continue to show up in english.

  18. - The problem is that all the developers, moderators and beta testers live in countries in which the native tongue is english. And my native tongue is not english. Although I have no problem reading english and german. That's why I found many language related bugs in CCleaner, Speccy and Defraggler.

    - I did the following on my dutch system (see my signature for the system setup)

    - Installed CC v5.45.

    - Perhaps I removed CC v5.45 ?? (I can't remember anymore)

    - Installed CC v5.44.

    - Installed CC v5.46.

     

×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.