Search Issue Tracker

Fixed in 2020.1

Fixed in 2019.3

Votes

0

Found in

2018.3.0a1

Issue ID

1210322

Regression

No

-profiler-maxusedmemory cmdline option doesn't work

Profiling

-

-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

Add comment

Log in to post comment

All about bugs

View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.