Use built-in callback cancellation from later #115
Merged
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.
Closes #114.
Previously, instead of cancelling the callback immediately, the canceller function would simply assign
func <<- NULL
. That would make the actual callback (which in turn callsfunc()
) effectively a no-op, but it would still exist and consume memory.This change uses the built-in later callback cancellation added in 1.0.0.
With this change, the test code from #114 (comment) does not leak.
Output:
Note: Using the CRAN version of pool (0.1.5), I tried using a smaller
idleTimeout
, as in the following:I expected it to release the memory after 2 seconds, but that doesn't seem to be the case, and I'm not sure why.