#225 configuration change detection problematic?

[Jeremiah]

UltraDefrag was constantly locking up. A quick look at Process Monitor and it was constantly reading/writing to ultradefrag.log and options.lua. All I had done was to make a minor change to options.lua in PSPad. Closing PSPad did not resolve the issue.

The log file is attached. It appears as if ultradefrag is constantly thinking a configuration change has been made.

------------------
System Information
------------------
      Time of this report: 6/6/2016, 11:27:15
             Machine name: (removed)
         Operating System: Windows 10 Pro 64-bit (10.0, Build 10586) (10586.th2_release_sec.160422-1850)
                 Language: English (Regional Setting: English)
      System Manufacturer: MSI
             System Model: MS-7818
                     BIOS: BIOS Date: 05/11/15 17:25:36 Ver: V1.11B0
                Processor: Intel(R) Core(TM) i7-4770K CPU @ 3.50GHz (8 CPUs), ~3.5GHz
                   Memory: 16384MB RAM
      Available OS Memory: 16328MB RAM
                Page File: 16263MB used, 7199MB available
              Windows Dir: C:\WINDOWS
          DirectX Version: 12
      DX Setup Parameters: Not found
         User DPI Setting: Using System DPI
       System DPI Setting: 96 DPI (100 percent)
          DWM DPI Scaling: Disabled
                 Miracast: Not Available
Microsoft Graphics Hybrid: Not Supported
           DxDiag Version: 10.00.10586.0000 64bit Unicode

[Jeremiah]

Also attaching options.lua, since that was the other file involved.

[Dmitri Arkhangelski]

Thank you, I'll try to fix this bug before the next release.

[AyrA]

I have the same issue without having made any configuration changes.
Interestingly the problem only appears when scanning the drive containing the temp files which is not the C: drive in my setup.

Log repeats itself quickly with these two lines:

2017-08-15 05:49:14.947 INFO: ConfigThread::Entry: configuration has been changed
2017-08-15 05:49:14.955 INFO: winx_set_dbg_log: log_path = \??\C:\Users\Administrator\Desktop\Tools\ultradefrag-portable-7.0.2.amd64\logs\ultradefrag.log

[Dmitri Arkhangelski]

Thank you for feedback, the bug will be fixed in the next release.