Search Issue Tracker
By Design
Votes
0
Found in
2022.3.12f1
2023.1.19f1
2023.2.0a19
Issue ID
UUM-54667
Regression
No
"A VisualElement of type 'UnityEngine.UIElements.TextElement' attempted to allocate 105528 vertices, which exceeds the limit of 65535 vertices per VisualElement" is thrown when TextField is annotated with TextAreaAttribute and is too long
How to reproduce:
- Open the attached project "EditorTextAreaLengthLimitRegression.zip"
- Select SampleScene>LotsOfText in the Hierarchy window
Expected results: No errors are thrown
Actual results: "A VisualElement of type 'UnityEngine.UIElements.TextElement' attempted to allocate 105528 vertices, which exceeds the limit of 65535 vertices per VisualElement" is thrown
Reproducible with: 2022.3.12f1, 2023.1.19f1, 2023.2.0a19
Not reproducible with: 2021.3.31f1, 2023.2.0a20, 2023.2.0b16, 2023.3.0a11
Reproducible on: Windows 10 22H2
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
- 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
- Placeholder asset is not loaded with Advertisement Legacy sample when using the latest version of the package
Resolution Note:
This is a known limitation of TextCore (used by IMGUI text fields), in 2022.x. 2023+ removes this limitation. The fix, however is not simple and is too risky to backport to 2022.
Note, also, that even in 2021, as far as I know, the limitation was still there. Text would just be cut off at the end after too many characters. The only difference was that there was no error to let you know this was happening.