Search Issue Tracker
Fixed in 2022.2.X
Votes
0
Found in
2020.3
2021.2
2022.1
2022.1.0a12
Issue ID
1378339
Regression
No
Allocations under EditorOnly ProfilerMarkers are not properly hidden when GetComponent is used for a non-existent component
How to reproduce:
1. Open the user's attached project
2. Open scene Scenes/SampleScene
3. Go to Window -> General -> Test Runner
4. In the newly opened Test Runner window, select the "EditMode" tab and click "Run All"
5. Go to Window -> General -> Test Runner again to observe the outcome of the test
6. Go to Window -> Analysis -> Profiler
7. In the CPU Usage Module's Hierarchy, enter "NoGC" in the search bar
8. Select the sample "NoGCMarkerUnderThisOneWhenFilteringOutEditorOnlyMarkerName" and press F
9. Observe the child samples
Expected result: the test passes, and the Profiler sample "NoGCMarkerUnderThisOneWhenFilteringOutEditorOnlyMarkerName" contains no GC.Alloc child samples
Actual result: the test fails, and the observed sample has a GC.Alloc child sample
Reproducible with: 2020.3.23f1, 2021.2.4f1, 2022.1.0a16
Could not test with: 2019.4.33f1 (error CS0246: The type or namespace name 'RawFrameDataView' could not be found)
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
- Additional settings dropdown in Terrain Overlay is not grayed out for painting modes with no extra settings
- Inconsistent Terrain brush Opacity values between Scene view and Inspector
- [Usability] No separated opacity for the different types of Terrain brushes
- [Quest] Pitch Shifter causes audio degradation on Quest 2 devices when sped up
- "GUI Error: Invalid GUILayout" and "NullReferenceException" are thrown when adding Scenes to "Scenes in Baking Set" in Adaptive Probe Volumes
Resolution Note (fix version 2022.2):
Fixed in 2022.2.0a10