Search Issue Tracker
Fixed in 2021.2.X
Votes
0
Found in
2020.3
2020.3.0f1
2021.1
2021.2
Issue ID
1321964
Regression
No
[Profiler] ProfilerRecorder gives invalid values in standalone Build
Steps to reproduce:
1. Download and open project "ProfilerRecorderBugTest.zip"
2. Make sure that "ProfilerScene" is open
3. Enter Play Mode
4. Notice the ProfilerRecorder values in Game View
5. Exit Play Mode
6. Go to File -> Build Settings and ensure “Scenes/ProfilerScene” is set for “Scenes in Build”, if not hit “Add Open Scenes”
7. Click “Build and Run”
8. Notice the ProfilerRecorder values in the Build
Expected Result: All values displayed by the ProfilerRecorder are greater than 0 MB
Actual Result: ProfilerRecorder displays “GPU Memory Usage”and “GPU Reserved Memory” as 0 MB
Reproducible with: 2020.3.2f1, 2021.1.0f1, 2021.2.0a10
Could not test with: 2018.4.33f1, 2019.4.23f1 (ProfilerRecorder not available)
Notes:
Issue was reproducible on MacOS Catalina(10.15.7) and on Windows 10
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
- [OpenGLES][XR] Zooming in on the camera's URP opaque texture causes "double vision" on Quest in OpenGLES3
- “[Worker0] Could not generate preview image“ error when opening macOS native plugin in the Inspector with Architecture to build for set to ARM 64-bit
- [iOS] Application.absoluteURL is empty on Awake/Start when opening via deep link with Splash Screen disabled
- Crash on MemoryManager::Deallocate when rapidly calling Addressables.LoadAssetAsync
- Crash on physx::shdfnd::atomicIncrement when adjusting values on a character controller component after entering Play mode in Prefab edit mode
Resolution Note (fix version 2021.2):
The issue was fixed in the documentation (https://docs.unity3d.com/Manual/ProfilerMemory.html)