Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix #155 #157

Merged
merged 9 commits into from
Sep 22, 2023
Merged

Fix #155 #157

merged 9 commits into from
Sep 22, 2023

Conversation

yoshuawuyts
Copy link
Owner

Fixes #155. The bug was that we were unconditionally marking a field as "done" in our TryJoin implementations, and then branched on the output value, with only one branch writing a value.

Our drop impl assumed that if a value was marked as "done" that the field was populated. But that wasn't true if TryJoin returned with an error, meaning it would attempt to drop uninitialized memory.

This affects all three TryJoin implementations since they're subtle adaptations of one another. I believe this bug was introduced as part of the work towards #137. We should release a patch release as soon as we've merged this PR.

@yoshuawuyts yoshuawuyts merged commit 0c0c1bc into main Sep 22, 2023
@delete-merged-branch delete-merged-branch bot deleted the fix-ub branch September 22, 2023 15:36
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

TryJoin on tuple trying to free a null pointer
1 participant