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 [2021/09/05 20:45] – gordonj | bugs_known_issues [2022/11/20 11:08] (current) – [Bugs & Known Issues] johnsanc | ||
|---|---|---|---|
| Line 1: | Line 1: | ||
| - | ====== Known Issues ====== | + | ~~NOTOC~~ |
| + | ====== | ||
| - | * If you run out of disk space during | + | <WRAP tip>Help us help you! If you find a bug or experience |
| - | | + | <WRAP important> |
| - | * A fix operation on a 7z file can leave orphaned files in the 7z cache directory. It appears these orphaned files are then completely ignored | + | ===== Bugs ===== |
| - | | + | ^ # |
| - | + | | 1 | Logic | If you generate fixDats on directories that are using the Single Archive | |
| - | | + | | 2 | Minor | The DatVault DAT " |
| + | | 3 | Minor | The Compress action is missing the filesize | ||
| + | | 4 | Logic | Empty directories and 0 byte files will be deleted during a fix when the branch is locked in the tree | | | ||
| + | | 5 | Crash | A hard crash can occur during a fix due to " | ||
| + | | 6 | Logic | A " | ||
| + | | 7 | Crash | A hard crash can occur during a scan or fix due to "The process cannot access | ||
| + | | 8 | Crash | A hard crash can occur during | ||
| + | | 9 | Crash | A hard crash can occur if you do not have a DatRoot folder present and you try to add a directory | ||
| + | | 10 | Crash | A filesystem error will be thrown if RomVault tries to ZipMove an archive while it is open in another application ([[https:// | ||
| + | | 11 | Crash | A hard crash can occur if you attempt a fix without a ToSort directory ([[https:// | ||
| + | | 12 | Minor | Recompressing to RV7Z shows a status of TrrntZipping | ||
| + | | 13 | Crash | A hard crash can occur when trying to write a file that is only a case sensitive rename. (screenshots: | ||
| + | | 14 | Logic | A " | ||
| + | | 15 | Crash | A hard crash can occur when RV tries to do a fix from a directory that is no longer accessible due to a case sensitivity difference. This may be a larger race condition issue where RV attempts to reference a folder or file before | ||
| + | | 16 | Logic | A "Light Cyan" to ToSort fix status is not accounted for. ([[https:// | ||
| + | | 17 | Crash | A hard crash can occur if an MIA submission times out ([[https:// | ||
| + | | 18 | Logic | CMP DATs are interpreted with incorrect character encoding. (screenshots: | ||
| + | | 19 | Minor | The in-app update notification to 3.5.0 does not work. | ||
| + | | 20 | Crash | A crash will occur if a user finds an MIA rom but the DatVault server is unreachable. ([[https:// | ||
| + | | 21 | Crash | A crash can occur while scanning an archive with the error " | ||
| + | | 22 | Logic | Sometimes a fix can end early and look complete, however the percentage is not 100%. This also results in a state where RV appears to show fix sources (orange/ | ||
| + | | 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 | ||
| + | | 25 | Crash | A "Start index cannot be less than zerp" | ||
| + | | 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 " | ||
| - | * If you generate fixDats on directories that are using the Single Archive setting with "Add SubDirs if multiple roms" then RomVault will crash with an error. The text reports will not cause a crash, but the reports will not include any information from the directories using Single Archive. This may also occur under other directory setting scenarios but this is unconfirmed. | ||
| - | * DATs with zero entries are automatically selected in the tree after a DAT Update, even if the DATs did not change. | + | ===== Known Issues ===== |
| - | | + | ^ # |
| + | | 1 | Fixes from 7z archives to Uncompressed sets do not use the 7z cache | ||
| + | | 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. | ||
| + | | 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:// | ||
| + | | 4 | ||
| + | | 5 | If a fix only consists of removals to ToSort, the percentage complete and progress bar stay at 0% ([[https:// | ||
| + | | 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:// | ||
| + | | 7 | A "File changed, rescan needed" | ||
| + | | 8 | An " | ||
| + | | 9 | An " | ||
| + | | 10 | RomVault | ||
| + | | 11 | There is a memory leak with mono 6.8.. upgrade to a newer version at [[https:// | ||
| - | * 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. | + | ===== Linux Specific - Issues ===== |
| - | | + | ^ # |
| + | | 1 | DATVault takes approximately 45 seconds to load and displays a black screen | ||
| + | | 2 | DATVault initially loads with no DATs. Closing the window and reopening can resolve the issue. ([[https:// | ||
| + | | 3 | DATVault groups filter sometimes shows with a black box ([[https:// | ||
| + | | 4 | DATVault | ||
| + | | 5 | DATVault checkboxes in the main DAT grid always appear checked ([[https:// | ||
| + | | 6 | Clicking external links in the DATVault UI causes a " | ||
| + | | 7 | Generating a fixDAT can cause a crash if no directory | ||
| + | | 8 | Sometimes the tree view can disappear when navigating around. Example: If you have one tree that's expansive, scroll down, then switch | ||
| + | | 9 | A hard crash with a "file already exists" | ||
| + | | 10 | The Game details and ROM details grids do not display the & character correctly. | ||
| - | * Files without read permissions are completely skipped by RomVault with no indicators. Ideally these files should be flagged with a blue status. | + | ===== TorrentZip UI ===== |
| - | * RomVault throws a " | + | ^# |
| - | + | |1|A crash will occur if a file has an invalid or missing timestamp | | | |
| - | * Missing counts in the tree and summary panes include ROMs that are in blue locked status. For example, an unneeded locked file will count as missing even if you have all other ROMs marked as " | + | |2|A CorruptZip error will occur if disk space runs out | | |
| - | + | |3|Cannot handle multiple files with the same name but different extensions when going from File > ZIP| | | |
| - | * If RomVault does not have proper access to a directory, scanning | + | |
| - | + | ||
| - | * The Dat Info pane can display information that does not reflect what is selected in the tree. This can be reproduced by navigating | + | |
bugs_known_issues.1630899958.txt.gz · Last modified: 2021/09/05 20:45 by gordonj