Search Issue Tracker
Fixed in 2021.2.X
Votes
0
Found in
2021.1.0a1
2021.2.0a2
Issue ID
1306180
Regression
Yes
[Linux] Non-matching Profiler error thrown on clicking the "Restore Defaults" option when Target Selection is Editor
Editor thrown Non-matching Profiler errors on clicking the "Restore Defaults" option under "Profiler Module" dropdown when "Target Selection" is "Editor", refer to the attached video
Steps to repro:
1. Create a new Project.
2. Window > Analysis > Profiler
3. Profiler Window > Target Selection > Editor
4. Profiler Window > "Profiler Module" > Restore Defaults > Click
Actual Result:
"Non-matching Profiler" error thrown on selecting Restore Default option
Expected result: "Profiler Module" dropdown Restore on selecting Restore Default option
Reproducible in:
2021.2.0a2, 2021.1.0b2, 2021.1.0a2
Working Fine in:
2021.1.0a1
Environment: Occurs only on Linux
Tested on Ubuntu 18.04 LTS
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Deployment fails with unexpected status code 0 0 when deploying a Cloud Code module
- Sprite Atlas Samples throw multiple warnings when changing the original Editor verion
- Deleting 2D Lights while Lighting Explorer is open throws “GUI Error” and “NullReferenceException” errors in the Console window
- "Couldn't open file for reading" error occurs when running binary2text on a file larger than 2 GiB
- AssetReference Variable Asset Reference Type is tied to list position and will produce unexpected results when creating or duplicating AssetReference Variables
Add comment