Search Issue Tracker
Won't Fix
Won't Fix in 2022.2.X
Votes
1
Found in
2020.3.34f1
2021.3.5f1
2022.1.7f1
2022.2.0a13
Issue ID
UUM-2370
Regression
No
Crash when clicking on a large json file in the Project window
Reproduction steps:
1. Open the user's attached project
2. Click on the file "Assets/OS_Topo_Building_Large.json"
Expected result: File gets selected
Actual result: Fatal Error window is thrown and Editor crashes
Reproducible with: 2019.4.35f1, 2020.3.27f1, 2021.2.10f1, 2022.1.0b4, 2022.2.0a3
Note:
- 2020.3 stream crashes with a bug reporter
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
- 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
- Placeholder asset is not loaded with Advertisement Legacy sample when using the latest version of the package
- Addressables content build fails but the Player build is successful when building a development build
Resolution Note:
Thank you for reporting a bug to Unity.
We have reviewed the issue carefully, and in this case the team is unable to prioritize fixing this bug. There are a number of reasons we make this decision, including the impact and severity of the issue across our user and customer base, and the possibility that future plans may solve the problem in a different way, or that a workaround for the bug may be available.
Today we will be closing this case. Thank you again for taking the time to report this issue, and please let us know if there is anything else that changes the impact or severity of this issue.
Resolution Note (2022.2.X):
Thank you for reporting a bug to Unity.
We have reviewed the issue carefully, and in this case the team is unable to prioritize fixing this bug. There are a number of reasons we make this decision, including the impact and severity of the issue across our user and customer base, and the possibility that future plans may solve the problem in a different way, or that a workaround for the bug may be available.
Today we will be closing this case. Thank you again for taking the time to report this issue, and please let us know if there is anything else that changes the impact or severity of this issue.