Search Issue Tracker
Won't Fix
Votes
0
Found in
6000.0.45f1
6000.1.0b13
6000.2.0a8
Issue ID
UUM-102301
Regression
Yes
The project hangs upon opening it when importing the "discrete_rank2_vector_v2_0.onnx" file
How to reproduce:
1. Open the “OnnxProject.zip“ project
2. Observe the behavior
Expected result: The Editor opens
Actual result: The Editor gets stuck on the launch screen
Reproducible in: 6000.0.36f1, 6000.0.45f1, 6000.1.0b13, 6000.2.0a8
Not reproducible in: 2021.3.50f1, 2022.3.61f1, 6000.0.35f1
Reproduced on: Windows 11 Pro (24H2), Windows 10, Mac Intel 15.4.1
Not reproduced on: No other environment tested
Notes:
- The importer gets stuck on this line: {{“Start importing Packages/com.unity.ml-agents/Tests/Editor/TestModels/discrete_rank2_vector_v2_0.onnx using Guid(b6c7faadd10084c3995ad9fff7aa8c54) (ScriptedImporter)"}}
- Seems to be reproducible only with this project
- Opening the project a second time usually yields the expected results. To reproduce, delete the project and re-extract it.
- In pre-regression versions, the project opens with many ML Agent package-related issues, so they could have an impact on the reproduction reliability
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
- Required SpriteMask class (ID 331) is stripped when "Strip Engine Code" is enabled
- “Maximized serialized file backup not found” error is thrown when minimizing a window in a newly opened project
- Build stack trace contains invalid lines when building with IL2CPP using scripts with delegates containing generic types in the signature
- Entities Systems window has a “Show Full Player Loop” dropdown which does nothing when clicked after enabling “Show Full Player Loop”
- Entities Hierarchy Search “Show/Hide” button’s Lens Icon is blurry when the Editor is on an external monitor
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.