Search Issue Tracker
Fixed
Fixed in 2022.3.62f1, 6000.0.48f1, 6000.1.0f1, 6000.2.0a9
Votes
0
Found in
2022.3.59f1
6000.0.41f1
6000.1.0b9
6000.2.0a6
Issue ID
UUM-99274
Regression
No
Crash on _platform_memmove when a moving GameObject is selected in the Scene view while in Play Mode
Reproduction steps:
- Open the attached “NAVB-138 Simple Repro.zip“ project
- Open the scene
- In the Enemy game object, make sure the Repro Crash toggle is on
- Make sure the Enemy game object is selected and that scene view is open so that gizmos are drawn
- Enter play mode
Reproducible with: 1.1.5 (2022.3.59f1), 2.0.6 (6000.0.41f1, 6000.1.0b9, 6000.2.0a6)
Reproducible on: macOS Sequoia 15.3 (M2 Ultra), macOS Sequoia 15.3.1 (M1) (user’s)
Not reproducible on: Windows 10 (22H2)
First few lines of the stack trace:
#0 0x0000019c71aa5c in _platform_memmove
#1 0x000001060f8d6c in NavMeshDebugDraw::vertex(float, float, float, unsigned int, float, float)
#2 0x000001060f1034 in DrawNavMeshAgent(NavMeshAgent const&)
#3 0x000001060f03b0 in DrawNavMeshAgentGizmo(Object&, int, void, Texture2D, RectT<float>)
#4 0x00000105c54b4c in GizmoManager::DrawActiveGizmos(dynamic_array<GizmoManager::ActiveGizmo, 0ul>&)
#5 0x00000105c54e74 in GizmoManager::DrawGizmos(GizmoSubset)
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Redoing creation of Sub Scenes and Cube GameObjects in Hierarchy throws “Assertion failed on expression: 'targetScene != nullptr’” error in Console window
- Selecting “New Sub Scene” after assigning “New Scene” in Sub Scene Script Component throws “Destroying GameObjects immediately is not permitted” in the Console window
- Shader Graph "Zoom Step Size" can be set to 0 even though the zoom still works
- Enabling/Disabling the Deprecated Nodes doesn't apply to the opened Shader Graph unless any Variable is added to the Blackboard
- Group Selection title text size is smaller in renaming than the actual font size
Add comment