Reproduction steps:
1. Open the attached “IN-112437” project
2. Open the Build Profiles window (File > Build Profiles)
3. Build the Project
4. Launch the built Player using this command: “./clomper.exe -native-leak-detection EnabledWithStackTrace”
5. Press the “Quit” button in the Player
6. Open and observe the Player.log

Expected result: No warnings are printed out
Actual result: Memory Leak warnings are printed out

Reproducible with: 6000.0.57f1, 6000.2.3f1, 6000.3.0b1

Reproducible on: Windows 11
Not reproducible on: No other environments tested

Notes:
- Received warnings:
{{GarbageCollector disposing of ComputeBuffer. Please use ComputeBuffer.Release() or .Dispose() to manually release the buffer.}}
{{GarbageCollector disposing of GraphicsBuffer. Please use GraphicsBuffer.Release() or .Dispose() to manually release the buffer.}}
{{Leak Detected : Persistent allocates 367 individual allocations.}}
{{Internal: There are remaining Allocations on the JobTempAlloc. This is a leak, and will impact performance}}
- Discussion: https://discussions.unity.com/t/memory-leak-in-gpu-resident-batcher/1639304