Search Issue Tracker
Won't Fix
Votes
0
Found in
2021.3.44f1
2022.3.48f1
6000.0.22f1
6000.1.0a7
7000.0.0a3
Issue ID
UUM-83239
Regression
No
Light Explorer Search functionality has no character limit
Steps to reproduce:
- Open a Unity Project
- Open the Light Explorer at Window > Rendering > Light Explorer
- Copy a large amount of text (Lorem Ipsum Generator)
- In the search field in the Light Explorer, hold down Ctrl + V to continuously paste the text
Actual results: The text is continuously pasted. The Window (and Editor) will start to get slow and laggy, and may start a loading loop that doesn't appear to end
Expected results: There is a character limit that stops too much text from being added to the search field
Reproducible with versions: 6000.0.22f1, 2022.3.48f1, 2021.3.44f1, 7000.0.0a3
Not reproducible with versions: -
Can’t test with versions: -
Tested on (OS): Windows 10/11
Notes:
- On earlier versions (2021.3 and 2022.3), the text is still continuously pasted, however it can appear that it isn't due to the way the search field works. The Window and Editor will still get laggy.
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
- var VisionOSEDRHeadromm has a comma instead of a dot when building with Metal Rendering App Mode and local OS localization is set to German
- IAP Catalog remove product “x” and add product “+” buttons are not consistent with other remove and add buttons in the Editor
- Performance issues in Play Mode when quickly hovering the mouse cursor over Hierarchy GameObjects
- Frame Debugger displays incorrect output when FidelityFX Super Resolution or Spatial-Temporal Upscaler is used with Temporal Anti-aliasing or Subpixel Morphological Anti-aliasing
- Crash with “Fatal Error! The file ‘MemoryStream’ is corrupted!” when adding a large number in Font Character Rects Size field
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.