Search Issue Tracker

Duplicate

Votes

1

Found in

13.0.2

14.0.2

Issue ID

UUM-131898

Regression

No

Error “ArgumentException: Key: -61254 is not present.“ is present when pooling/despawning prefabs

2D Animation

-

Reproduction steps:
1. Open the attached project "ReproProj"
2. Open the “/Assets/Scenes/SampleScene.unity” Scene
3. Enter the Play Mode
4. Wait ~5-20 seconds (objects are continuously spawned/despawned via pooling)

Expected result: No Errors exist
Actual result: Error “ArgumentException: Key: -61254 is not present.“ is present

Reproducible with: 13.0.2 (6000.3.3f1), 14.0.2 (6000.4.0b3, 6000.5.0a4)
Could not test with: 6000.0.65f1 (Objects are not spawned)

Reproducible on:
Play Mode

Not reproducible on:
Windows Standalone Player

Testing environment: Windows 10 Enterprise 21H2
Not reproducible on: No other environment tested

Notes:
- The issue started appearing after upgrading to 6000.3
- Callstack points to UnityEngine.U2D.Animation.TransformAccessJob.UpdateTransformIndex / DeformationManager.Update
- Reproducible in a clean/minimal project
- Prefab contains SpriteRenderer and SpriteSkin (SpriteSkin has no bones assigned)
- This looks like internal DeformationManager NativeHashMap key becomes invalid after despawn/disable

  1. This is a duplicate of issue #UUM-131697

    "System.IndexOutOfRangeException" and "ArgumentException" errors are thrown when activating and deactivating multiple sprites in an animation

  1. Resolution Note:

    Thank you for reporting a bug to Unity.

    We have reviewed the issue and found it is a duplicate of an existing bug already logged in our system. To keep things organized and ensure the issue is properly prioritized, we have linked your report to the original case.

    We will now close this report as a duplicate, but the original bug remains open and under review. Your input has been noted and helps us better understand the impact of the issue. If anything changes regarding its severity or impact, please let us know.

    Thank you for helping us improve Unity!

  2. Resolution Note:

    Thank you for reporting a bug to Unity.

    We have reviewed the issue and found it is a duplicate of an existing bug already logged in our system. To keep things organized and ensure the issue is properly prioritized, we have linked your report to the original case.

    We will now close this report as a duplicate, but the original bug remains open and under review. Your input has been noted and helps us better understand the impact of the issue. If anything changes regarding its severity or impact, please let us know.

    Thank you for helping us improve Unity!

Log in to vote on this issue

Add comment

Log in to post comment

All about bugs

View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.

Latest issues

See all new issues