Feedback - Bugs & Issues

The fixing progress bar and percentage indicator do not seem to account for the "Compress" action. Steps to reproduce: Add some zips and a few large uncompressed files to ToSort which are needed for a fix. The issue is easiest to identify if the uncompressed files will be last to be fixed. Scan, Find, Fix Notice that the progress bar and percentage will say 100% before all of the uncompressed files are compressed to their final destination

CHD verification cannot be cancelled

Reproducible

Enhancement

Cancelling a scan does not stop verification of the current CHD. A scan cancellation should immediately stop the CHD verification process. Steps to reproduce: Place a large CHD file in a ToSort Start a scan of the ToSort Immediately try to stop the scan Notice that RV still continues to decompress and hash the chd and will not cancel the scan until its complete.

RV should halt if a path is inaccessible

Reproducible

Network File Error

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. Steps to reproduce: Start with a fresh RV instance Map a network drive and assign it as a ToSort. Reproducing this issue works best if the ToSort contains a lot of files and directories. Scan the mapped network drive ToSort After the scan is complete, start the scan again and quickly disconnect the mapped network drive as RV is traversing directories Notice that RomVault will continue the scan without error but will erase any previously scanned info for future directories leaving only empty directory references in the cache.

7z cache grows too large

WIP Testing

With RV 3.7.0 the 7z cache seems to fill up without any deletions. One user reported a 7z cache that grew to over 700 GiB. The files in the 7z cache should be deleted after the archive they are needed for has been written.

Sorting resets during a fix

Reproducible

General UX

When RomVault is fixing, the sort order of the ROM Details and Game List grids keep resetting every few seconds. This behavior makes browsing your collection difficult when a fix is running. The user-specified sort order should persist while a fix is running. Steps to Reproduce: Add the Sony PS3 redump DAT and set the rules to use Single Archive without subdirs so that the dat contents are predominately displayed in the rom details grid Start a fix that should take a few minutes to complete (to be able to have enough time to reproduce the issue) Navigate to the PS3 dat in the tree and try to scroll the rom details grid to view set content - notice the grid snaps back to the top every few seconds Try to sort by various columns in the rom details grid - notice the sorting resets every few seconds.

Linux and Windows cache seem to use the same directory separators

Need Info

Core

Linux

copying cache from a windows to linux machine still gives backward slashes. so it seems those are hardcoded

Crash occurs when attempting to delete a file open by another process

Reproducible

RomVault will hard crash during a fix when it attempts to delete a file open by another process. The error is: "The process cannot access the file XXXXX because its being used by another process". When this occurs the cache becomes out of sync with the filesystem and the user must rescan after closing and reopening RomVault. Steps to reproduce: Put a .bin file in your ToSort directory Load a DAT that requires that .bin file Mount the .bin file in Daemon tools so it is locked by that process. Scan, Find, Fix RomVault will crash on the deletion attempt of the .bin file

Incorrect "Scanning Dirs" percentage in window title when scanning

Reproducible

When I scan my "To Scan" directory the window title of the progress dialog shows "Scanning Dirs - 100% complete". But it just started, it is not 100% complete and therefore confusion when looking at the title in the Windows taskbar it would help if I see values like 75% or 90%. Or no percentage value. It is for sure a minor, more or less cosmetic bug... Suggested solutions (if I did not misunderstood the intention): 1) Just show "Scanning Dirs" or "Scanning Dirs - in progress..." 2) Update the title with the correct percentage value each time the value increases 3) Show instead the current dir name that is currently scanned, e.g. "Scanning dir: To Sort" with a relative (short) path that might work... Steps to reproduce: Scan a ToSort directory with many subdirs Notice as its scanning the title bar says 100% complete

Scanning progress window does not show accurate scanning position

Reproducible

Enhancement

The scanning progress window shows statistics in the upper right corner. This statistic shows the position of the last file scanned in relation to the total number of files in the directory. This is not a useful metric because many files in the directory may already be scanned. Ideally this metric should be: "Number of files scanned including the current file" / "Total files that need to be scanned in the directory" Note in this case "scan" is described as files that need to be hashed because they are either new or their timestamps have changed compared to the RV cache. Steps to reproduce: Start a scan across your RomRoot and ToSort directories on your primary instance of RV Watch the scanning window carefully and note the file progress counter, it is not intuitive to the user and does not appear reflective of what is actually happening

If a fix only consists of removals to ToSort, the percentage complete and progress bar stay at 0%

Reproducible

Enhancement

Steps to reproduce: Start with a fresh RV instance Place some files that do not match any dat in your romroot Scan files Find and fix Notice the progress percentage does not update for any removals to ToSort

Crash occurs with “unexpected network error” when a mapped network drive experiences latency

Cannot Reproduce

Network File Error

If a mapped network drive is under heavy load, spun down, or otherwise has excessive latency, then RV will crash during a fix targeting that network drive. Steps to reproduce: Introduce excessive latency to a mapped network drive (Unsure the best way to do this consistently, but the error was observed when there was a heavy network load, it maybe possible to reproduce by disabling your network adapter or unmounting the drive in the middle of the fix) Perform a fix that targets the network drive A crash will occur if the latency is too great Expected behavior: RomVault should display a halting error and update the cache (screenshot)

Partial sets are unexpectedly built with certain DAT settings

Reproducible

Settings

Using the following DAT settings, RV will create partial sets during a fix which is not expected: Archive Type: File Single Archive: No Subdirs (or conflicts only) Keep Only Complete Sets: Enabled In this case, when a user is using the "File" archive type, they are likely wanting to prevent subdirectories and prevent storing discs with incomplete tracks.

Crash occurs when attempting to delete a file with insufficent permissions

Reproducible

RomVault will crash if it attempts to delete a file that is does not have permission to delete. The easiest way to reproduce this issue is with an unraid share: Setup RV with a dat and file that would match something in a ToSort that resides on an unraid share Ensure the owner of the file is nobody/users Change the permissions of the file to 0644 instead of the usual 0666 Scan and fix RV should crash when attempting to delete the file with 0644 permissions

Case sensitive deduped removals cause file not found error

Reproducible

There are cases where RV will associate the wrong character case file with a DAT. If the dat references a character case that is different from what is actually on the case-sensitive filesystem, when this file is removed due to a "not needed because deduped" scenario RV will error. Subsequent L2 scans do not correct the character case in the cache. File not found error: Light Cyan status indicating the deduped file is not needed there. Notice the upper case ASTRONEER text: Actual file on filesystem. Notice lowercase Astroneer text:

Hard crash doing Fix ROMs before Find Fixes

WIP Testing

RV will crash with an "object reference not set to an instance of an object" error under the following conditions: Add a DAT and scan a few roms for that DAT in their proper location so they are green status Open DAT settings and change the compression from the default of deflate to zstd, ensure "convert while fixing" is ticked After saving the dat settings, click fix roms without first doing find fixes. Notice RV crashes with an error similar to below

RV CMD displays UI related error messages during CHD scan

WIP Testing

RV CMD seems to display errors when scanning chds.

Excessive SMB chatter causes fix to stall

WIP Testing

Core

In some setups using Samba shares, RV seems to generate a significant amount of chatter which causes significant delays during fixing and can render RV essentially unusable on large collections. When using Wireshark, there is evidence that RV is also requesting directories and their ancestors that are not in scope. RV 3.7.1 WIP2 is the first build with this issue.

Logic error for DB found file does not match

WIP Testing

As of RV 3.7.2, some dats with non-standard characters cause an error during fixing. The error states: "Logic error trying to find the file we are fixing XXXXX DB found file does not match"

Make New Folder button enabled for Master Dirs in DatVault

WIP Testing

When adding new dats from DatVault, the the Make New Folder button is enabled even when Master Dirs is selected. The button should be disabled since the rest of the datroot tree is grayed out.

Crash if Cache ToSort unavailable

Reproducible

If the cache ToSort is unavailable, RV will crash when it is attempted to be used for fix. Steps to reproduce: Map a network drive and assign it as a cache ToSort Disconnect the network drive Scan a solid 7z archive that is also needed for a fix Find / Fix, and notice RV crashes when trying to write to the Cache ToSort

Crash due to illegal characters in path during fix

Need Info

RV will crash when a fix is performed on a file in an archive that has illegal characters in its path. In this case the double quote is invalid. When this archive is fixed, a crash occurs:

Category subdirs do not work properly on auto-created directories

Reproducible

Settings

The category subdirectories feature does not work when its applied to an auto-created datroot directory. Put multiple redump dats into a directory Apply the category subdirs setting on one of the dats Notice the category subdirs are not applied Refresh all dats and notice the settings are applied. Remove the dat rule and apply, and notice the settings remain Refresh all dats, and notice the settings are applied.

Zero byte files are extracted to 7z cache

WIP Testing