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.
Issue
I ran into a problem with constantly growing
RSS
usage, when processing thousands of images sequentially. I used theMALLOC_ARENA_MAX
environment variable, which improved the situation, but after the end of the image processing phase (in my application), a large chunk of memory was left by the process ~1.5GB. I started to investigate why this was happening and came to the conclusion thatMALLOC_ARENA_MAX
does not completely eliminate memory fragmentation. So I decided to replace the standard allocator inlibvips
, withjemalloc
, which is made for such use cases. As a result, this completely fixed the situation, and minimizedRSS
usage as much as possible (as iflibvips
had never been used).Solution
I think it would be useful to add such a feature to the description so that people don't waste their time researching such problems.