kp: bump version_kp to v1.0.2 -> v1.1.0 - #270
Merged
Merged
Conversation
Thanks for merging daanx#265. A follow-up: v1.1.0 was released during daanx#265's review and the pin was not moved before the merge. Tags at or below v1.0.2 can hand the same block to two live users on Linux (and Windows): the cold free path's teardown check folded to a constant false anywhere but macOS, so a thread past its own allocator cleanup pushed into an already-destroyed cross-dealloc batch. macOS was never exposed -- which is precisely why this suite's Linux CI is the matrix that matters here. Reproducer: 17/44 failures before, 0/44 after -- ours, not in this suite (it needs a preloaded program whose pthread_key destructor frees; no bench here has one, which is also why CI is green on either pin). It ships in kamepoolalloc as tests/alloc_tsd_exclusivity_test.cpp if you want to look.
mjp41
approved these changes
Sep 2, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Thanks for merging #265. A follow-up: v1.1.0 was released during #265's review and the pin was not moved before the merge. Tags at or below v1.0.2 can hand the same block to two live users on Linux (and Windows): the cold free path's teardown check folded to a constant false anywhere but macOS, so a thread past its own allocator cleanup pushed into an already-destroyed cross-dealloc batch. macOS was never exposed -- which is precisely why this suite's Linux CI is the matrix that matters here.
Reproducer: 17/44 failures before, 0/44 after -- ours, not in this suite (it needs a preloaded program whose pthread_key destructor frees; no bench here has one, which is also why CI is green on either pin). It ships in kamepoolalloc as tests/alloc_tsd_exclusivity_test.cpp if you want to look.
Build integration is unchanged: v1.1.0's
CMakeLists.txtis identical to v1.0.2's and the samecmake -B out/cmake --build outproducesout/libkamepoolalloc$extsoin the same place, so no other hunk is needed.CI on my fork:
kpis green on fedora and alpine. The reds in that run are the ones #269 is addressing (je / hm / tcg / mesh / sn, and the ubuntu base container); ubuntu'skpjob did not run because its base container failed first.