Search Issue Tracker
Not Reproducible
Votes
0
Found in
1.5.0-pre.2
Issue ID
UUM-132094
Regression
Yes
"Resolve of invalid GC handle" errors are spammed when installing the AI packages
How to reproduce:
1. Create a new project
2. In the Unity toolbar, click the "AI" button
3. Click "Agree and install Unity AI"
4. Observe the results
Expected results: No errors are thrown
Actual results: "Resolve of invalid GC handle" errors are spammed
Reproducible with: 1.5.0-pre.1 (6000.3.3f1, 6000.4.0b4, 6000.5.0a3)
Not reproducible with: 1.0.0-pre.20 (6000.3.3f1, 6000.4.0b4, 6000.5.0a3)
Reproducible on: macOS Tahoe 26 (M1)
Not reproducible on: No other environment tested
Note: 1.0.0-pre.20 has different errors on install
Full error: Resolve of invalid GC handle. The handle is from a previous domain. The resolve operation is skipped.
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
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
Resolution Note:
Thank you for reporting a bug to Unity.
We have investigated the issue but were unable to reproduce it with the information provided. This can happen due to differences in environment, project setup, or steps taken.
We will close this case for now. If you're able to share additional details such as different projects, steps, hardware/software configuration, or logs - please let us know, and we'll be happy to re-evaluate.
Resolution Note:
Thank you for reporting a bug to Unity.
We have investigated the issue but were unable to reproduce it with the information provided. This can happen due to differences in environment, project setup, or steps taken.
We will close this case for now. If you're able to share additional details such as different projects, steps, hardware/software configuration, or logs - please let us know, and we'll be happy to re-evaluate.