Memory isn't freed when creating and returning large objects in concurrent function about deco HOT 1 CLOSED

That is a great catch actually! This bug had some logical errors along with it, so pretty important to have resolved. The commit I just made c8ecc63 should sort it out, although it's a pretty small change. Thanks for finding this!

If you're interested in what was going on, during the synchronized function execution deco keeps track of all the assignments that happen. This includes a reference to Pool's async result object, which will include a reference to the return result of the concurrent function. During each synchronization event, deco goes through the list and performs the assignments. Turns out I had forgotten to clear the list of assignments though! So every event would perform every assignment over again, and also caused this memory leak since it maintained a reference to all this.

Once again, really appreciate you finding this! Let me know if there is still some memory leak in your application or feel free to close this.

from deco.