Differences

This shows you the differences between two versions of the page.

--- bugs_known_issues [2021/09/05 16:18] – johnsanc
+++ bugs_known_issues [2021/09/05 20:45] – gordonj
@@ Line 1: / Line 1: @@
 ====== Known Issues ======
-  * If you run out of disk space during a fix that uses the 7z cache, RomVault with throw a friendly error. Upon dismissing this message a hard crash will occur with an error and the cache will become corrupted. RomVault will not start again until the corrupt cache file is removed.
+  * If you run out of disk space during a fix that uses the 7z cache, RomVault with throw a friendly error. Upon dismissing this message a hard crash will occur with an error and the cache will become corrupted. RomVault will not start again until the corrupt cache file is removed. (Kind of fixed in next release, running out of disk space is always a bad thing, but RV should no longer hard crash or corrupt the cache, but the cache will be out of date, as there is no space left to write out the latest cache, and a rescan will be required, once space has been made on the drive.)
   * If a file is in use by another process during a fix operation on that file, RomVault will crash and throw an error. At this point the cache will be out of sync with the files on disk and a rescan will be needed.
@@ Line 19: / Line 19: @@
   * Corrupt archive icons are only displayed at levels above the directory where the corrupt archive resides. E.g. an archive sitting in the base directory of your ToSort will not appear as corrupt when clicking on ToSort in the tree.
-  * Files can be deleted in certain scenarios with unrecommended directory settings. For example, if you map a directory in your RomRoot to a ToSort directory then a fix operation will delete files that RomVault thinks are not needed because they reside elsewhere. In this case the directory deleted from and the location of the undeeded roms are the same. An extra check is needed to prevent unwanted deletions.
+  * Files can be deleted in certain scenarios with unrecommended directory settings. For example, if you map a directory in your RomRoot to a ToSort directory then a fix operation will delete files that RomVault thinks are not needed because they reside elsewhere. In this case the directory deleted from and the location of the undeeded roms are the same. An extra check is needed to prevent unwanted deletions. (Extra checks have been added to the next release to make this less likely to delete files in this incorrect user case.)
   * Files without read permissions are completely skipped by RomVault with no indicators. Ideally these files should be flagged with a blue status.