Search Issue Tracker
By Design
Votes
0
Found in
2020.3.45f1
2021.3.19f1
2022.2.9f1
2023.1.0b4
2023.2.0a4
Issue ID
UUM-29468
Regression
No
Unity crashes on SpriteRendererTransformChangedJob when adding a new GameObject to the Scene
Steps to reproduce:
1. Open the attached project “IssueProject“
2. Open the “Assets/Scenes/SampleScene.unity“ Scene
3. Enter Play Mode
4. Select the “Playground“ GameObject in the Hierarchy window
5. In the Inspector window click the “Add Agents“ button (might need to click it multiple times)
Expected result: New GameObjects are added to the Scene
Actual result: Unity crashes with a different stack trace each time
Reproducible with: 2020.3.45f1, 2021.3.19f1, 2022.2.9f1, 2023.1.0b4, 2023.2.0a4
Reproducible on: Windows 10
Stack trace:
0x00007FF7D6EB8DDA (Unity) SpriteRendererTransformChangedJob
0x00007FF7D70B0A27 (Unity) BatchJob
0x00007FF7D6F31E2B (Unity) JobQueue::Exec
0x00007FF7D6F3216E (Unity) JobQueue::ExecuteJobFromHighPriorityStack
0x00007FF7D6F32804 (Unity) JobQueue::ProcessJobs
0x00007FF7D6F3484F (Unity) JobQueue::WorkLoop
0x00007FF7D710AD86 (Unity) Thread::RunThreadWrapper
0x00007FFD56557614 (KERNEL32) BaseThreadInitThunk
0x00007FFD583626A1 (ntdll) RtlUserThreadStart
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
- The UI Toolkit TreeView Items get clipped when resizing the Game view window when Scale with Screen Size is set as the Scale Mode in the Panel Settings
- Components of a Prefab instance lose their values that are updated with the Reset() method when entering Play Mode
- UI Builder Broken Direct Asset Reference Overrides
- Universal 3D Sample project template takes a very long time to build.
- ShaderGraph tabs persist to projects that do not have that shader graph
Resolution Note:
Hi, we have investigated the project and found that the crash only occurs when the buffer is overflown.
When allocating more than the capacity of 'START_CAPACITY' can handle, it starts crashing as you are overwriting memory in semi-random places.
In the future when dealing with unsafe memory and crashes, try and run the editor with -debugallocator. It might hurt performance, but using this flag you will get errors in the console when accessing invalid memory.
We will keep make a note of the bug and see if we can improve our tools based on this case.