-
-
Notifications
You must be signed in to change notification settings - Fork 131
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
Adding an extremely large file to archive returns an error #816
Comments
With a suggestion from Discord, I managed to successfully add the file to the archive by dropping the file to the content folder directly. |
Ha
That's possible-- not sure how [whatever library LRR uses] works-- but yeah, probably not the case.
I believe LRR runs inside Docker/WSL on Windows, so that'd be why.
No worries! I don't know Perl at all, but I might use this as an opportunity to learn it. A few questions:
Also, it'd be helpful if you could link the file, so I can try to reproduce the issue. |
The problem file was a zip file which I compressed at the "Best" compression method of WINRAR with dictionary size of 32KB. I use the same settings for all my archives.
The largest single image is ~29mb and the smallest is just 665kb. Judging by the statistically inaccurate analysis method of eyeballing it, I'd say the vast majority of images are between 5-7mb. In total there are 1653 images.
The archive is called "toraisix Part 1" and it can be found in sadpanda (/2389953/ddcc780995/). I haven't ran into similar problems afterwards despite that the second largest archive file I have is just 30mb smaller while the largest single image in it is at a whopping 48mb. |
LRR Version and OS
0.8.90, Windows 11 Education version 22H2
CPU: i7-12700K
RAM: 32GB
Bug Details
Reproducable error when attempting to add one or more extremely large archives.
The compressed folder that I haven't been able to add by itself is 10GB.
Nipping this problem at the bud would be great since there are plenty of image sets that are over 9GB in size.
I don't have any computers available that would have even more RAM or a more powerful CPU, so I can't test if it is just a matter of hardware not being able to handle it. Honestly I doubt that would be the case, but I am not an expert by any means so that is still an option to consider.
Matching Logs
This would suggest that this might just be a me problem, but I haven't found the referred file so I could disable the read-only setting.
All signs point to it being in a Linux/Unix location but I am running Windows, so I can't find it.
Sorry for not being a programmer. I literally made a Github profile for this...
Screenshots
Following happens after trying to upload the archive again after failure.
Breaks the installation but is easily fixed with the built in re-installer.
The text was updated successfully, but these errors were encountered: