Search Issue Tracker
Won't Fix
Won't Fix in 6000.4.X
Votes
0
Found in
6000.0.59f1
6000.2.7f1
6000.3.0b4
6000.4.0a1
Issue ID
UUM-121028
Regression
No
Line Renderer Component position field allows large values, spamming “Assertion failed on expression” errors in the Console window
Steps to reproduce:
1. Create new Unity project using empty HDRP 3D or URP 3D Template
2. Create Empty GO in Hierarchy window
3. In Inspector add Line Renderer Component for Empty GO
4. In Line Renderer > Positions > Size > X value add “2222222222222222222222” in to the field
5. Observe the Console window
Actual results: “Assertion failed on expression: 'IsFinite(distanceForSort)’” errors are spammed in the Console window
Expected results: Value field should have a limit how many characters can be entered, there should be no errors in the Console
Reproducible with versions: 6000.0.59f1, 6000.2.7f1, 6000.3.0b4, 6000.4.0a1
Tested on (OS): Windows 11, macOS Silicon, Tahoe 26.0 (M1)
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
- Invalid Clip Method
- WebGPU error with Fantasy Kingdom and GPU Resident Drawer
- WebGPU fails with height fog in Fantasy Kingdom
- Crash on UndoManager::RegisterUndoInternal when applying added GameObjects to a Prefab
- [Asset Bundles] A new bundle hash is not generated when the name of a serialized field is changed
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 (6000.4.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.