- This topic has 8 replies, 1 voice, and was last updated 6 months, 2 weeks ago by
.
-
Posts
-
System environment:
Operating System: x64 Windows 11 (10.0.22631)
AnyTXT version: 1.3.1380 (with OCR)
AnyTXT installation mode: The software is actually located in “D:\Program Files\AnyTXT Searcher”, and is located in “C:\Program Files\AnyTXT Searcher” through a symbolic link.
The AnyTXT configuration file and index data are located on another hard disk, and the configuration file “config.db” is located in “D:\Program Files\AnyTXT Searcher” through a symbolic link.
The index update period configured for AnyTXT is “every 4 hours”.
AnyTXT is additionally configured with more file types that need to be indexed.The system also has Shadow Defender installed to quickly eliminate traces of usage.
The following faults were found:
Within a few minutes of each system startup, AnyTXT starts to behave like a “full reindex”. The entire process lasts about 40 minutes in the above system environment. During this time, the CPU is under constant load.
At the same time, the following content was found in the log:
[253: indexprivate.cpp] Index file *********.ati has an exception 1011 / 1026 / 1001.The known temporary solution is to delete the old index data and then manually completely rebuild the index. However, the failure occurs again soon (maybe more than ten days later, or the next day). That is to say, in terms of the observed phenomenon, manually re-indexing completely will not prevent AnyTXT from “consuming CPU and taking a long time to index” behavior after every system startup.
To avoid privacy leaks caused by incomplete desensitization, if you need AnyTXT logs for fault tracking, please contact me via email.
Additional notes:
1. The folder where the AnyTXT log is located is also symbolically linked (“C:\ProgramData\Anytxt”) and is actually located at “D:\ProgramData\Anytxt”;
2. “Every time the system starts” has nothing to do with the index update cycle configured by AnyTXT, which means that even if the interval is less than 4 hours, the above phenomenon will recur every time the system starts.Errata:
AnyTXT’s index data changes its storage location through its own configuration options (Options -> Index Manager -> Index Store Path) instead of migrating through symbolic links.The path where the AnyTXT configuration file and index data are located is excluded by Shadow Defender, and the shadow mode has been exited, so there will be no problem of “forced index rebuilding due to undoing changes to related files”.
1. I recently removed all symbolic links, returning all files to their default paths (including all files under “C:\ProgramData”, and “C:\Program Files\AnyTXT Searcher\config.db”);
2. The configured index interval is still “every 4 hours”;
3. Execute a “manual full re-index” after undoing all symbolic links, and then restart the computer (first time);
4. Wait for the fault to reappear. This “index (faulty)” lasts about 1.5 hours;
5. Restart the computer immediately after completing the previous step (for the second time, it has been more than 1.5 hours but less than 4 hours since the last time the computer was restarted and indexing was completed).
Test results: After restarting the computer for the second time, AnyTXT started to behave like a “full re-index” again.—-
All files under “C:\ProgramData”, as well as “C:\Program Files\AnyTXT Searcher\config.db” are in the exclusion list of Shadow Defender, and the above test was performed when the system entered shadow mode.
My assumption: Since the above path is not affected by Shadow Defender, AnyTXT may somehow and somewhere record the last index time. Eventually whenever I start or restart the computer, automatic indexing should be done at the interval I configure. Start automatically (the appropriate start depends on the last index time or the last change index cycle) rather than with every system startup.
In addition, I also found that the duration of automatic indexing after each system startup ranges from about ten minutes to about 1.5 hours.Since revoking the symbolic link did not solve the problem, it has now been restored to the status of the symbolic link, and the index automatic update cycle has been changed to “Never”.
Impact of this failure:
The behavior of AnyTXT upon system startup is accompanied by consistently high performance consumption and causing fan noise.Hello,friend.
Are you in China?
If you are in China, please contact WeChat customer service longmate4U.
Customer service will help you solve problems.
Thank you.
No, because I don’t have a WeChat account.
However I have found a workaround that works for me: configure AnyTXT’s index update cycle to “Never”, and then set the startup mode of the AnyTXT service to “Manual”.
The result of this is: the AnyTXT service no longer starts automatically. Although AnyTXT no longer automatically updates the index at a fixed time after the system starts, it also does not perform long-term meaningless error indexing, and only needs to be manually performed once if the index needs to be updated later.
