Skip to main content

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

Required fields*

2
  • Can you please expand on the part where " the consumer needs to sequentially perform N "large" operations"? I don't seem to get the idea. What would be the issue with performing these N large operations sequentially by malloc'ing, consuming, and then free'ing the needed memory at each iteration? Commented Oct 31, 2023 at 11:26
  • 4
    @MehdiCharife I can't speak for all sorts of software, but for the specific case I handled - generating large chunks of simulated landscapes - it had several recursive steps that needed to allocate memory themselves. Recursively allocating memory needs some... special engineering to make work, and this usual format doesn't handle it that well. Commented Oct 31, 2023 at 11:31