Search Issue Tracker
Won't Fix
Votes
0
Found in
2017.3.0f1
Issue ID
973718
Regression
No
[Editor] Highlighter stops working if no component selected.
When you try to highlight a component that is not attached to the selected gameobject,or when you try to run highlighter without selecting any gameobject, it gets stuck in an infinite loop and never works again. (This can happen accidently)
Steps:
1. Create a new project.
2. Add attached script to the project. (HighlighterTester-1)
3. Go to Windows and Select "Highlighter Tester".
4. Click "Highlightby Prefixlabel" and then Click "Highlight by Content".
Note: Find "Highlighter recursion detected" warning in the console.
Now highlighter will not work until we re-open unity.
WorkAround:
Re-open Unity to use Highlighter.
Reproduced on: 2017.1.1f1, 2017.1.2p3, 2017.2.0f3, 2017.3.0f1
Notes:
- Appears on both Mac and Windows.
- Appears always.
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
- [Android] Stage information is not logged when Log Shader Compilation is enabled
- [Vulkan] The memory allocation increases rapidly when there are multiple (three or more) Real-Time Reflection Probes in the Scene
- [macOS] Library folder of the opened project can be deleted which leads to the crash
- “Default Scene” dropdown field contains a spelling mistake “Default Builtin”
- Editor crashes on PPtr<Mesh> after adding Text Mesh and Cloth Components to the same GameObject
Resolution Note:
This particular case has been investigated thoroughly and we have decided, in the interests of protecting the stability and features of Unity for users that rely upon the affected versions, to not address this fix. We understand that this will cause problems for some users, and fully intend for an existing, or forthcoming upgrade to provide the solution that you need