Fix igbinary_serialize incorrectly deduplicating arrays/objects #289
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.
... That are freed
For example, this can be seen when
__serialize
returns an array thatcontains a temporary array.
Before, because the result of
__serialize
was immediately freed,another array could be created with the exact same memory address,
and igbinary would incorrectly assume they're duplicates.
Incorrect deduplication can be avoided by keeping references to all
serialized arrays/objects around in memory.
TODO: Add additional checks/tests for references.(done)This may affect the performance of serialization.
Fixes #287
Based on #288