Search Issue Tracker
Fixed in 2020.1.X
Fixed in 2019.3.X
Votes
0
Found in
2018.3.0a1
Issue ID
1210322
Regression
No
-profiler-maxusedmemory cmdline option doesn't work
-profiler-maxusedmemory has no effect in standalone player builds.
This prevents users to configure optimal value to maintain the lowest profiler overhead
- https://forum.unity.com/threads/profiler-deep-profile-in-build-shows-bogus-data.794223
- https://forum.unity.com/threads/crash-when-using-deepprofiling.796806/
Repro steps:
1. Create an empty project.
2. Add a GameObject
3. Create a script which does Debug.Log(Profiler.maxUsedMemory.ToString()) in Awake.
4. Attach script to the created GO.
5. Build standalone Player
6. Ran Player with -profiler-maxusedmemory 12345678
Actual result:
The log outputs 16MB
Expected result:
The log outputs 12345678
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Search field in UI Builder's Library has no character limit
- Changing the value in UI Builder by dragging increases it by a few thousand points when reaching the borders of the screen
- ARM64 architecture DLL incorrectly copied instead of x64 when building for Windows x64
- Crash on TypeTreeIterator::GetNode when opening a specific folder
- Crash on WriteSerializedAssetsV2 when (re)entering the Play Mode in a specific project when IEnumerator Start() is used
Add comment