Search Issue Tracker
Won't Fix
Votes
0
Found in
2021.3.31f1
2022.3.11f1
2023.1.17f1
2023.2.0b14
2023.3.0a10
Issue ID
UUM-53651
Regression
No
Editor freezes when inserting a bug number to the array of points in “Handles.DrawAAPolyLine”
How to reproduce:
1. Open the user’s attached “DrawAAPolyLineBug.zip” project
2. In the Hierarchy window, select “DrawAAPolyLineBug” GameObject
3. In the Inspector window, insert “80000” to the Point Count Text Field
4. Observe the result
Expected result: Editor doesn’t freeze
Actual result: Editor freezes
Reproducible with: 2021.3.31f1, 2022.3.11f1, 2023.1.17f1, 2023.2.0b14, 2023.3.0a10
Reproduced on: macOS 13.5.2 (Intel)
Not reproducible on: No other environment tested
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
- Unity CIL Linker fails on Player build when persistent listeners have "<" and ">" in their XML attribute names
- ”Lighting data asset ‘LightingData’ is incompatible with the current Unity version…” warnings are thrown when saving Indoors (URP) and Outdoors (URP) Scenes as Scene Templates
- [iOS] The screen blinks when transitioning from custom to Unity splash screen
- [macOS] ”Ignoring depth surface load action as it is memoryless” warnings are thrown when taking Game View Snapshot
- UI Builder Inspector scrolls back up when changes on an expanded but not fully displayed Inspector tab are saved
Resolution Note:
The editor is freezing because it is trying to process a huge amount of vertices. Given time, or a more powerful machine, it will eventually succeed. This would be true of any type of work on the CPU or GPU, it is not specific to the Handles API.
There is an argument to made that Handles.DrawAAPolyLine could be optimized further, but for the typical use case it is working as intended.
Another option would be to artificially clamp the amount of vertices that Handles functions accept, which is difficult to reason about without setting target hardware specifications or unnecessarily limiting functionality for som users.
Given that this is easily worked around on user side, closing this ticket as won't fix.