Search Issue Tracker
Fixed in 6000.0.47f1
Fixed in 6000.0.X, 6000.1.0b15, 6000.2.X, future release
Votes
0
Found in
2022.3.40f1
6000.0.13f1
6000.1.0a7
6000.2.0a1
Issue ID
UUM-77619
Regression
No
"Object.InstantiateAsync" continues instantiating GameObjects when Play Mode is exited
How to reproduce:
1. Open the “InstantiateAsync.zip“ project
2. Open the “SampleScene“
3. Enter Play Mode
4. Exit Play Mode
5. Expand the “Instantiator“ GameObject
6. Observe the Hierarchy
Expected result: No more Cube GameObjects are being created
Actual result: Cube GameObjects are still being created
Reproducible in: 2022.3.40f1, 6000.0.13f1
Could not test in: 2021.3.41f1 (No “Object.InstantiateAsync” method)
Reproduced on: Windows 11 Pro (23H2)
Not reproduced on: No other environment tested
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
Add comment