bugs_known_issues
Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
| bugs_known_issues [2022/08/02 12:51] – [Table] johnsanc | bugs_known_issues [2022/11/20 11:08] (current) – [Bugs & Known Issues] johnsanc | ||
|---|---|---|---|
| Line 2: | Line 2: | ||
| ====== Bugs & Known Issues ====== | ====== Bugs & Known Issues ====== | ||
| - | |**💡 TIP:** \\ Help us help you! If you find a bug or experience a crash not on this list, please report it on the [[https:// | + | <WRAP tip>Help us help you! If you find a bug or experience a crash, please report it on the [[https:// |
| + | |||
| + | <WRAP important> | ||
| ===== Bugs ===== | ===== Bugs ===== | ||
| Line 31: | Line 33: | ||
| | 23 | Logic | An unaccounted for combination of ROM statuses can occur during a fix and throw and error ([[https:// | | 23 | Logic | An unaccounted for combination of ROM statuses can occur during a fix and throw and error ([[https:// | ||
| | 24 | Minor | Ampersand characters in file and path names are not displayed in the scanning status window | | 24 | Minor | Ampersand characters in file and path names are not displayed in the scanning status window | ||
| + | | 25 | Crash | A "Start index cannot be less than zerp" error can occur when trying to make a Full DAT from the RomVault root ([[https:// | ||
| + | | 26 | Crash | A crash will occur if the temp archive is open by another process when RomVault tries to rename it ([[https:// | ||
| + | | 27 | Minor | A "file has changed" | ||
| + | | 28 | Minor | The " | ||
| ===== Known Issues ===== | ===== Known Issues ===== | ||
| - | ^# | + | ^ # |
| - | |1|Fixes from 7z archives to Uncompressed sets do not use the 7z cache| | | + | | 1 |
| - | |2|If a path becomes inaccessible during a scan (E.g. mapped network drive), RV will continue to scan and erase information of previously scanned files. Ideally RV should halt if a path is inaccessible.| | | + | | 2 |
| - | |3|Browsing subfolders in a ToSort during a scan/fix will change the DAT Info panel back to the root of the ToSort every few seconds. ([[https:// | + | | 3 |
| - | |4|The 7z cache logic can result in scenarios where the cache directories can accumulate before deletions occur. This should be optimized to keep a minimum amount of data uncompressed in the 7z cache directories at any given time. ([[https:// | + | | 4 |
| - | |5|If a fix only consists of removals to ToSort, the percentage complete and progress bar stay at 0% ([[https:// | + | | 5 |
| - | |6|[WIP BUILD] ZipMove is sometimes not used if the archive to be moved contains a 0 byte file. This occurs if the zip to be moved resides in a path that comes before the destination directory alphabetically. (E.g. DirA -> DirB: ZipMove not used. DirB -> DirA: ZipMove is used.) ([[https:// | + | | 6 |
| - | |7|A "File changed, rescan needed" | + | | 7 |
| - | |8|An " | + | | 8 |
| - | |9|An " | + | | 9 |
| - | |10|RomVault will attempt to scan archives even if the timestamp of the archive did not change. Example: A dat file contains zips as files, so you rename all your zips to *.zip_ to prevent RV from scanning the contents. After fixing the zips have the proper extension in the proper place. However, now if you scan that directory the zip contents will be hashed, which is unwanted. | | | + | | 10 | RomVault will attempt to scan archives even if the timestamp of the archive did not change. Example: A dat file contains zips as files, so you rename all your zips to *.zip_ to prevent RV from scanning the contents. After fixing the zips have the proper extension in the proper place. However, now if you scan that directory the zip contents will be hashed, which is unwanted. |
| + | | 11 | There is a memory leak with mono 6.8.. upgrade to a newer version at [[https:// | ||
| ===== Linux Specific - Issues ===== | ===== Linux Specific - Issues ===== | ||
| - | ^# | + | ^ # |
| - | |1|DATVault takes approximately 45 seconds to load and displays a black screen in the process ([[https:// | + | | 1 |
| - | |2|DATVault initially loads with no DATs. Closing the window and reopening can resolve the issue. ([[https:// | + | | 2 |
| - | |3|DATVault groups filter sometimes shows with a black box ([[https:// | + | | 3 |
| - | |4|DATVault will sometimes crash if loaded with login info saved in the config.xml |Ubuntu 20.04 | | | + | | 4 |
| - | |5|DATVault checkboxes in the main DAT grid always appear checked ([[https:// | + | | 5 |
| - | |6|Clicking external links in the DATVault UI causes a " | + | | 6 |
| - | |7|Generating a fixDAT can cause a crash if no directory is selected. RomVault attempts to save to a " | + | | 7 |
| - | |8|Sometimes the tree view can disappear when navigating around. Example: If you have one tree that's expansive, scroll down, then switch to a smaller tree the pane goes blank. You need to swap and swap back to get it to appear again. Basically it doesn' | + | | 8 |
| - | |9|A hard crash with a "file already exists" | + | | 9 |
| + | | 10 | The Game details and ROM details grids do not display the & character correctly. | ||
| ===== TorrentZip UI ===== | ===== TorrentZip UI ===== | ||
bugs_known_issues.1659469892.txt.gz · Last modified: 2022/08/02 12:51 by johnsanc