Search Issue Tracker
Not Reproducible
Votes
0
Found in
2021.1
2021.1.20f1
2021.2
Issue ID
1365922
Regression
No
Crash on UpdateAvatars when entering Play Mode
How to reproduce:
1. In the attached project, open the "Start" scene
2. Go into Play Mode
3. If Unity didn't crash, exit Play Mode and re-enter Play Mode (Usually crashes after couple of tries)
Reproducible with: 2021.1.23f1, 2021.2.0b14
Could not test with: 2019.4.31f1, 2020.3.19f1, 2022.1.0a10 (Errors in console)
First lines of stack trace:
0x00007ff6d2c19da6 (Unity) Animator::UpdateAvatars
0x00007ff6d2c15f94 (Unity) Animator::SetVisibleRenderers
0x00007ff6d329e0fe (Unity) EventManager::InvokeEventCommon
0x00007ff6d346583a (Unity) Renderer::RendererBecameVisible
0x00007ff6d3512b9e (Unity) SkinnedMeshRenderer::RendererBecameVisible
0x00007ff6d33664be (Unity) RendererScene::SceneAfterCullingOutputReady
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
- var VisionOSEDRHeadromm has a comma instead of a dot when building with Metal Rendering App Mode and local OS localization is set to German
- IAP Catalog remove product “x” and add product “+” buttons are not consistent with other remove and add buttons in the Editor
- Performance issues in Play Mode when quickly hovering the mouse cursor over Hierarchy GameObjects
- Frame Debugger displays incorrect output when FidelityFX Super Resolution or Spatial-Temporal Upscaler is used with Temporal Anti-aliasing or Subpixel Morphological Anti-aliasing
- Crash with “Fatal Error! The file ‘MemoryStream’ is corrupted!” when adding a large number in Font Character Rects Size field
Resolution Note (2022.1.X):
It is no longer reproducible as the provided sample requires to log to a remote server which seems to be offline. The only way we could reproduce it would be to put the server back online or provide a sample that doesn’t require logging to that server.