Repository navigation
v0.17.3
pixtreme-transport 0.17.3: releasing the last reference of an open C output session closes it first. Native ABI 6 and CONFORMANCE_REVISION 6 are unchanged; the C ABI declarations and the public headers' declarations are unchanged, and programs and modules built against the 0.17.0, 0.17.1 or 0.17.2 public headers keep loading and pick up the new behaviour without being rebuilt.
- Output final release (issue #165): when the last reference of an output session handle is released while the session is open, the session now runs the same close sequence as an explicit close (stop the target, end the core encode and send threads,
join_target, finish core GPU work, return remaining values,close_target) before it releases the callbackcontext_owner. This matches the input session. An unopened output, or one that was explicitly closed and not reopened, does not call target hooks again. The hooks run synchronously on the thread that releases the last reference, so release it on the lifecycle caller, outside core threads and SDK callbacks. A final release consumes its reference even when the close fails and reports the failure (including a saved fatal) through its status; retry a failing close with an explicit close while you still hold a reference. Like an explicit close, a final release can wait indefinitely for hooks, real completions or GPU work, including during interpreter shutdown. The comments inpixtreme/transport/c/exit.h,c/session_entrance.handsession/session.hstate the contract. - Wheels: CPython 3.12 and 3.13,
manylinux_2_28_x86_64, built with the imagepixtreme-transport-wheel:cuda13-manylinux_2_28-5dfc35d6a2b1fromwheel-build/at this tag. Each wheel ships the shared librarylibpixtreme_transport.so.6, the public C and C++ headers, the CMake package configuration and thetestingpackage. CUDA's runtime is linked statically; the NVIDIA driver library is not included. - Verify the assets with
sha256sum -c SHA256SUMS.