Reproduction steps:
1. Open the attached “IN-105792_Pose - Repro.zip“ project (link in the internal comments)
2. Open the “PoseDetection” scene
3. Enter Play mode
4. While observing the Console, wait until the first video of the sequence starts playing in the Game view

Expected result: Skeletal poses are being detected continuously in the Game view and no errors are thrown in the Console
Actual result: The detected skeletal pose freezes on the first frame in the Game view and a NullReferenceException is thrown in the Console

Reproducible with: 2.3.0 (6000.0.55f1, 6000.2.0b13, 6000.3.0a4)

Reproducible on: Windows 11 Pro (24H2)
Not reproducible on: No other environment tested

Notes:
- The user has reproduced the issue with both the BackendType.CPU and BackendType.GPUCompute for the Workers. The provided project, which the CQA tested, uses the BackendType.CPU
- Could not test in a new project (due to the project’s complexity and the specificity of the issue)
- The user was able to resolve the issue by not creating a new detector every time the image source changed and asked a question about this on their personal GitHub post (link in the internal comments)
- After exiting Play mode, a warning appears in the Console that says: “Found unreferenced, but undisposed CPUTensorData which might lead to CPU resource leak”
- Reproducible in the Player