Coping with large solid archives #5
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
skips the initial part of the strem this avoiding caching uncompressed files preceeding the one we actually have to decode
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Hi this is a fix for a memory problem I found when uncompressing large archives. You might want to revise my changes and eventually merge them on your master.
Also, this does not seem the only problem I have encountered. There is also an overflow issue with the sdk bindings. Unfortunately I am quite a beginner and I am not sure how to debug the binding. For example, is there a way to compile the code with debug information under linux and then step into the functions?
Thanks
Emilio