alpha
Login
or
Join now
nateholland.bsky.social
/
PoseDetection
Star
0
Fork
0
Atom
Configure Feed
Issues
Pull Requests
Commits
Tags
Feed URL
Select the types of activity you want to include in your feed.
This repository has no description
Star
0
Fork
0
Atom
Configure Feed
Issues
Pull Requests
Commits
Tags
Feed URL
Select the types of activity you want to include in your feed.
Overview
Issues
Pulls
Pipelines
PoseDetection
/
posedetection
/
at
release-4.15.1
2 folders
1 file
virtualintern
fix: retain camera CVPixelBuffer + throttle GC on iOS (v4.15.1)
1mo ago
f255e0dd
src
fix: retain camera CVPixelBuffer + throttle GC on iOS (v4.15.1) Two iOS-side fixes for use-after-free crashes (kima downstream + sample app on iPad/iPhone 17 Pro) and the resulting cpu_resource warnings. * CameraController.captureOutput now CFRetains the CVImageBufferRef synchronously on the camera output queue before dispatch_async, with a matching CFRelease in the worker's finally block (and an outer bufferEnqueued guard for the dispatch-failed path). Without this the K/N closure dereferenced freed memory inside FrameProcessor's first CFRetain because AVCaptureVideoDataOutput recycles sample buffers the moment the delegate returns. * The dispatch_async closure no longer captures any per-frame ObjC reference. Orientation and mirrored flag are snapshotted into local primitives, lastCaptureConnection is written directly on the camera output queue (idempotent — connection is constant for the session), and analyseBufferForAll is invoked with captureConnection = null since both overrides are non-null. * GC.collect() is now called every 10 frames (~3 Hz at 30 fps) instead of every frame. K/N's auto-GC trigger is too lazy at this allocation rate so a periodic synchronous collect is still required, but cutting the frequency 10× clears the sustained CPU advisory iOS 26 was raising on the camera queue.
1 month ago
tools
Revert "chore: revert iOS pose to Vision (v4.15.1)" This reverts commit 2df79f72f8d71ed17dcafa64c0b69fe5334663a1.
2 months ago
build.gradle.kts
fix: retain camera CVPixelBuffer + throttle GC on iOS (v4.15.1) Two iOS-side fixes for use-after-free crashes (kima downstream + sample app on iPad/iPhone 17 Pro) and the resulting cpu_resource warnings. * CameraController.captureOutput now CFRetains the CVImageBufferRef synchronously on the camera output queue before dispatch_async, with a matching CFRelease in the worker's finally block (and an outer bufferEnqueued guard for the dispatch-failed path). Without this the K/N closure dereferenced freed memory inside FrameProcessor's first CFRetain because AVCaptureVideoDataOutput recycles sample buffers the moment the delegate returns. * The dispatch_async closure no longer captures any per-frame ObjC reference. Orientation and mirrored flag are snapshotted into local primitives, lastCaptureConnection is written directly on the camera output queue (idempotent — connection is constant for the session), and analyseBufferForAll is invoked with captureConnection = null since both overrides are non-null. * GC.collect() is now called every 10 frames (~3 Hz at 30 fps) instead of every frame. K/N's auto-GC trigger is too lazy at this allocation rate so a periodic synchronous collect is still required, but cutting the frequency 10× clears the sustained CPU advisory iOS 26 was raising on the camera queue.
1 month ago