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
- A submenu disappears on MacOS when the MenuItem method argument "isVariableFunction" is set to "false" and priority argument is set to "-1"
- The Sprite Library Editor window has an incorrect order of Sprites when the Sprites are reordered and the order saved
- Tilemap Tiles do not get lit up unless the Light Range is greater than the distance between the position of the Tile before the transformation and the Light Source when the Tile is transformed with Tilemap.SetTransformMatrix method
- The Editor and "Reloading Domain" windows are frozen when entering Play Mode
- Crash when attempting to create a custom FMOD DSP unit
Add comment