Search Issue Tracker
Fixed
Fixed in 2021.3.37f1, 2022.3.23f1, 2023.2.20f1, 6000.0.0b13
Votes
0
Found in
2021.3.30f1
2022.3.10f1
2023.1.14f1
2023.2.0b10
2023.3.0a5
6000.0.0b11
Issue ID
UUM-49060
Regression
No
Wrong number is returned when using “Target.Pool.CountActive” in ObjectPool if objects are destroyed
How to reproduce:
1. Open the user’s attached “unity object pool error.zip” project
2. Enter Play Mode
3. In the Hierarchy, select “ObjectPoolTester” GameObject
4. In the Inspector window, press the “Pull from pool” button 11 times
5. Press the “Return from pool” button 11 times
6. Observe the “Active objects” number under the “According to ObjectPool” text
Expected result: Number is 0
Actual result: Number is 1
Reproducible with: 2021.3.30f1, 2022.3.10f1, 2023.1.14f1, 2023.2.0b10, 2023.3.0a5
Reproduced on: macOS 13.4.1 (Intel)
Not reproducible on: No other environment tested
Note: “Target.ManualCountActive” returns correct number
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- “[Worker0] Could not generate preview image“ error when opening macOS native plugin in the Inspector with Architecture to build for set to ARM 64-bit
- [iOS] Application.absoluteURL is empty on Awake/Start when opening via deep link with Splash Screen disabled
- Crash on MemoryManager::Deallocate when rapidly calling Addressables.LoadAssetAsync
- Crash on physx::shdfnd::atomicIncrement when adjusting values on a character controller component after entering Play mode in Prefab edit mode
- [Rendering Debugger] [NewInputSystem] Debug Overlays in Play mode throws InvalidOperationException when using New Input System
Resolution Note (fix version 6000.0.0b13):
Fixed in: 6000.0.0b13
Resolution Note (fix version 2022.3.23f1):
Fixed in: 2022.3.23f1
Resolution Note (fix version 2021.3.37f1):
Fixed in: 2021.3.37f1