Search Issue Tracker
Won't Fix
Won't Fix in 6000.5.X
Votes
0
Found in
2022.3.69f1
6000.0.65f1
6000.3.3f1
6000.4.0b3
6000.5.0a5
Issue ID
UUM-131695
Regression
No
Crash on GameObject::QueryComponentByType when opening a specific project
How to reproduce:
1. Open the attached “IN-128305” project
2. Observe the crash
Reproducible with: 2022.1.22f1, 2022.3.69f1, 2023.2.0a19
Not reproducible with: 6000.0.65f1, 6000.3.3f1, 6000.4.0a3, 6000.5.0a4
Fixed: 2023.2.0a20
Reproduced on: Windows 11, macOS 15 (user reported)
Not reproduced on: No other environment tested
First few lines of the stack trace:
#0 0x00000102df15c8 in GameObject::QueryComponentByType(Unity::Type const) const
#1 0x00000103aa03b8 in UI::AddRenderersToCanvas(JobFence&, Transform const, UI::Canvas*, int&)
#2 0x00000103aa0198 in UI::Canvas::UpdateBatchOrder()
#3 0x00000103a9fd04 in UI::Canvas::UpdateBatches(bool)
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
- Shader Graph Category dropdown cannot be expanded/collapsed when clicking on the text
- Different text alignment in the column header in Entities "System" window
- Objects with Universal Render Pipeline/Particles/Lit shader are always lit up when changing their Rendering Layer Mask
- PolySpatial “Trying to set shader on a Material Variant.” error is printed in the console when entering Play Mode
- Error “Shader error in 'YSCloudCover': call to 'tex3D' is ambiguous at Assets/YSCloudCoverText.shader(606) (on d3d11)“ is present when compiling tex3D shader with DXC
Resolution Note:
Thank you for reporting a bug to Unity.
We have reviewed the issue carefully, and in this case, the issue does not warrant any further changes.
The issue is fixed in Unity 6 and 2023.3. In previous affected version, such as 2022.3 deleting the Library folder and reloading the project will fix the issue.
Resolution Note (6000.5.X):
Thank you for reporting a bug to Unity.
We have reviewed the issue carefully, and in this case, the issue does not warrant any further changes.
The issue is fixed in Unity 6 and 2023.3. In previous affected version, such as 2022.3 deleting the Library folder and reloading the project will fix the issue.