Jump to content
CCleaner Community Forums

dvdbane

Experienced Members
  • Content Count

    413
  • Joined

  • Last visited

Community Reputation

0 Neutral

About dvdbane

  • Rank
    Advanced Member

Profile Information

  • Gender
    Male

Recent Profile Visitors

906 profile views
  1. Sorry, i don't understand this question 😓 or you can use this step to test. I did test using this step too on other pc
  2. Hi @Winapp2.ini winapp2ool v1.2.7175.37819 weird thing happen when using trim for this location HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Foxit Software\Foxit Reader Detect=HKLM\Software\Foxit Software\Foxit Reader = trimmed(wrong) Detect=HKLM\Software\Foxit Software = not trim(correct) tested this location HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\SHAREit Technologies\SHAREit and winapp2ool trim correctly just for testing purpose, tested this location \SHAREit Technologies\SHAREit Tech and winapp2ool trim correctly [Foxit Reader **] LangSecRef=3021 Detect=HKLM\Software\Foxit Software\Foxit Reader Default=False
  3. one of the reason people login to this forum to report a problem try Analyze first and remove one by one what ccleaner detected till you get the Cleaner rule that cause the problem Report back here your finding
  4. can someone check again this entry? i don't use chrome much so i only test autofill and this entry remove autofill
  5. if i'm not mistaken, for locked files, bleachbit will schedule delete on reboot(Special operation)
  6. it doesn't matter if you're not using Google Chrome, as long as you're using chrome variant and use extension, that cleaning rule will make some extension lose settings or corrupted that will make a lot of user really mad esp Stylish/Stylus user which is why [Logs *] was modified i don't make the decision but if you need more explanation, then @APMichael can help with that
  7. didn't notice the modified entry until @siliconman01 mentioned it *.log and excludekey was removed from the entry [Logs *] due to issues #320
  8. 2.2. Write-Ahead Log (WAL) Files A write-ahead log or WAL file is used in place of a rollback journal when SQLite is operating in WAL mode. As with the rollback journal, the purpose of the WAL file is to implement atomic commit and rollback. The WAL file is always located in the same directory as the database file and has the same name as the database file except with the 4 characters "-wal" appended. The WAL file is created when the first connection to the database is opened and is normally removed when the last connection to the database closes. However, if the last connection does not shutdown cleanly, the WAL file will remain in the filesystem and will be automatically cleaned up the next time the database is opened. 2.3. Shared-Memory Files When operating in WAL mode, all SQLite database connections associated with the same database file need to share some memory that is used as an index for the WAL file. In most implementations, this shared memory is implemented by calling mmap() on a file created for this sole purpose: the shared-memory file. The shared-memory file, if it exists, is located in the same directory as the database file and has the same name as the database file except with the 4 characters "-shm" appended. Shared memory files only exist while running in WAL mode. The shared-memory file contains no persistent content. The only purpose of the shared-memory file is to provide a block of shared memory for use by multiple processes all accessing the same database in WAL mode. If the VFS is able to provide an alternative method for accessing shared memory, then that alternative method might be used rather than the shared-memory file. For example, if PRAGMA locking_mode is set to EXCLUSIVE (meaning that only one process is able to access the database file) then the shared memory will be allocated from heap rather than out of the shared-memory file, and the shared-memory file will never be created. The shared-memory file has the same lifetime as its associated WAL file. The shared-memory file is created when the WAL file is created and is deleted when the WAL file is deleted. During WAL file recovery, the shared memory file is recreated from scratch based on the contents of the WAL file being recovered.
  9. if removing wpndatabase.db break Microsoft Store Apps Live Tile feature. then i think *.db-shm;*.db-wal need to be remove too as it is created by wpndatabase.db and will be deleted automatically https://www.sqlite.org/tempfiles.html
  10. @Winapp2.ini got this error and winapp2ool crash when running offline while trying to setup winapp2.ini on my friend laptop no error when running online test function merge and trim, no problem, didn't test other features does this cause by not using dotnet 4.6 like issue #251 on github? win 7 sp1, dotnet 4.5.2
×
×
  • Create New...