Search Issue Tracker
Not Reproducible
Votes
0
Found in [Package]
0.2.5-preview.1
Issue ID
1274144
Regression
No
[Memory Profiler] Shaderlab data is not shown in Memory Profiler when a snapshot is captured
How to reproduce:
1. Open the attached project "profiler-shaderlab.zip"
2. In File > Build Settings, make sure that Assets/Scenes/SampleScene.unity is added to the Build
3. Build and Run
4. In the Editor, open Window>Analysis>Profiler
5. Connect the Profiler to the Player, click on the Memory module and take a sample
6. Note that Shaderlab can be seen in the sample (under Other > Rendering) and is using around 10Mb worth of memory
7. Open Window>Analysis>Memory Profiler
8. Connect the Memory Profiler to the Player, then capture and open a snapshot
Expected results: Shaderlab can be seen in the captured snapshot
Actual results: Shaderlab is not included in the captured snapshot
Reproducible with: 2019.4.10f1, 2020.1.6f1, 2020.2.0b3 (Memory Profiler 0.2.5-preview.1)
Could not test with: 2018.4.27f1 as URP is in its early preview state
Notes:
- The issue has been reproduced on Nintendo Switch and Windows Standalone
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
Add comment