Search Issue Tracker
In Progress
Votes
0
Found in
4.0.0
4.0.2
Issue ID
UUM-135678
Regression
Yes
Crash with multiple stack traces or freeze when entering Play Mode in a specific scene using ML Agents
How to reproduce:
1. Open the attached “IN-108928.zip” project
2. Open the “SampleScene”
3. Enter Play Mode
4. Exit Play Mode
5. Observe the crash
Reproducible in: 4.0.0 (6000.0.57f1, 6000.2.4f1, 6000.3.0b1)
Not reproducible in: 2.0.1 (6000.0.57f1, 6000.2.4f1, 6000.3.0b1)
Could not test with: 3.0.0 - compilation errors prevent reproduction when using this version
Reproducible on: Windows 10, Windows 11
Not reproducible on: No other environments tested
Notes:
- If the crash does not occur the first time, repeat steps 3-4
- When using 2.0.1, IndexOutORangeExceptions appear in the console instead of crashing
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