Search Issue Tracker
Fixed
Fixed in 1.1.0-exp.1
Votes
0
Found in [Package]
1.0.0-pre.1
Issue ID
PROFB-64
Regression
No
It is not possible to find objects of a specific type when using a Memory Profiler
Steps to reproduce:
1. Create and open an empty project
2. Go to the Package Manager and add a package by name: “com.unity.memoryprofiler”
3. Open Memory Profiler by going to Window → Analysis → Memory Profiler
4. Import user attached “Boat Attack (Windows)” snapshot to the Memory Profiler and open it
5. Go to the Unity Objects tab and observe the search bar
Expected result: Lets you filter the search (e.g. by name, by type)
Actual result: The search bar can only search for items that contain text in the target object's name
Reproducible with: 1.0.0-pre.1, 1.0.0 (2022.2.1f1, 2023.1.0a24)
Not reproducible with: 0.7.1-preview.1 (2020.3.43f1, 2021.3.16f1, 2022.2.1f1)
Reproduced on: macOS Monterey 12.2 (Intel)
Note: If testing with not reproducible version, on the 5th line go to the Objects and Allocations tab and observe filtering options
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- [Usability] Selecting Animations Clips in a Blend Tree's Motion List does not Visualize their Weight if all Weights have been enabled previously
- Unity Version Control “Create a new workspace” window text boxes expand vertically when inputting a very long text and covers the whole window
- A Blend Tree's Visualization is not repainted when a Blend Tree's Parameters change in Play Mode
- Cursor size and resolution is inaccurate when switching the 'Default Cursor' field
- Lightmapping delegate not called for first scene when baking via "-executeMethod" on editor launch
Add comment