I was trying to use the feature for indexing archive files, and I had several crashes and still having them.
update:
Using the logging feature i was able to find the file, it was a corrupted file.
So corrupted files causes this feature to crash Everything.
A mitigation solution:
- I don't know it if it is possible to add this as a quick fix release, but an "If condition" added to code that reads the archive, and if the archive is corrupted then skip it, add it to a text file for later processing, so the program wouldn't crash, this will save the time not redoing the same indexing every time Everything crashes.
- Maybe also a option to automatically save progress every number of scanned files, like every 500 scanned files. So even if it crashed, you still have the option to quickly resume the scanning, and also quickly pinpointing the corrupted file, and continue to find the next corrupted file.
I am using the latest version Version 1.5.0.1387a (x64), but the crash was also in the Version 1.5.0.1383a (x64).
Also I noticed that when I updated to 1.5.0.1387a (x64), my old the session including windows and tabs was not restored correctly. I had alot of windows and tabs opened before the update. But after the update I had only like 4 or 5 windows restored.
Any thoughts about these two problems void.
I have a question also void: how can I run a command line for every file in the search or every file I select, but not all at once ?
I mean :
1- I select files
2- I run the command line
3- Everything run the command line on first file, and waits until the command finishes. Like waiting for an exit code of "0", so it knows that the command line was successful
4- Everything runs the same command line again, and if an error occurs, then it will save it to a text or log file for later processing, then it will continue for other files so it doesn't lost its progress.
Can I achieve this use case ?