Repository navigation
Re-enable mmap on 32-bit architectures - #2000
Merged
Merged
Conversation
memmap2 v0.3.0 introduced a regression when trying to map files larger than 4GB on 32-bit architectures [1] which was subsequently fixed in v0.3.1 [2]. This commit bumps locked version of the memmap2 dependency to the current v0.5.0 and reverts fdfc418 to re-enable mmap on 32-bit architectures as a different approach to fixing [3]. This was tested to report matches from the end of a 5GB file using MinGW and Wine. [1] RazrFalcon/memmap2-rs@5e27122 [2] RazrFalcon/memmap2-rs@9aa838a [3] #1911
Contributor
Author
|
I would be grateful for a short feedback whether this is wanted at all. I think the root cause for the issues is highly likely to have been the bug in memmap2. Since that dependency has been bumped in the meantime, I don't think the workaround needs to be kept around. |
Owner
|
I think I buy it. Your research is enough to give me some confidence that this won't re-occur. If it does, we can re-apply the patch. |
This file contains hidden or 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
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.
memmap2 v0.3.0 introduced a regression when trying to map files larger than 4GB on 32-bit architectures which was subsequently fixed in v0.3.1.
This commit bumps locked version of the memmap2 dependency to the current v0.5.0 and reverts fdfc418 to re-enable mmap on 32-bit architectures as a different approach to fixing #1911.
This was tested to report matches from the end of a 5GB file using MinGW and Wine:
whereas still using memmap2 v0.3.0 but fdfc418 reverted would silently fail