-
-
Notifications
You must be signed in to change notification settings - Fork 93
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Bug] RomM gets stuck while triying to scan some roms (.7z extension related) #1211
Labels
bug
Something isn't working
Comments
Can you post the scan logs? |
Sorry, I post it on Discord and forgot to post it here to, here it is:
|
I have a similar issue with version 3.5.1. In my case, it's trowing an error when dealing with platforms containing .tar.gz files. No issues in other platforms. I can confirm that the error is not appearing when reverting to version 3.3.0.
|
adamantike
added a commit
that referenced
this issue
Oct 6, 2024
This change improves memory usage, by only keeping a single archive's member file in memory at a time during 7zip decompression. The `py7zr` library does not support streaming decompression yet, so this change is the best we can do for now. Potential fix for #1211, but it won't improve memory usage for single-file 7zip archives.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
RomM version
3.5.1
Describe the bug
It seems that if a rom have .7z extension and goes over certain size, RomM gets permanently stuck scanning that one rom.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
It shouldn't get stuck there, and should identify the rom correctly as (i think) was pre 3.5.0
The text was updated successfully, but these errors were encountered: