Search Issue Tracker
Won't Fix
Votes
0
Found in
2020.3.34f1
2021.3.4f1
2022.1.3f1
2022.2.0a16
Issue ID
UUM-4354
Regression
No
Standalone Profiler default memory is not enough warning logged when performing basic functions
How to reproduce:
1. Open up an empty 3D template project
2. Open up the Standalone Profiler from Window > Analysis > Profiler (Standalone Process)
3. Enter Play Mode in the Editor whilst recording for "Playmode" in the standalone Profiler
4. Save profiling information after 5 seconds of recording to binary file and observe Console
5. Change target between "Playmode" and "Editor" whilst recording a couple times and observe Console
Expected result: Saving and changing profiling targets function without warnings in an empty scene
Actual result: User is prompted to increase default memory for the Standalone Profiler when saving data, changing profiling targets and those warning seem to be logged randomly after performing those actions
Reproducible with: 2020.3.34f1, 2021.3.4f1, 2022.1.3f1, 2022.2.0a16
Couldn't test with: 2019.4.39f1 (No Standalone Profiler)
Error logged:
Stopping profiler. Profiler is not able to flush data to a file or socket and exceeded maximum allowed memory for buffering.
Please use Profiler.maxUsedMemory API or -profiler-maxusedmemory command line parameter to increase maximum allowed memory usage.
Using 536870913 bytes while Profiler.maxUsedMemory is 536870912 bytes.
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
- Inspector Ping does not fully encapsulate an element with an icon in the Project window
- “Property offset falls outside of range for type in GetPropertyData” errors are thrown when using MaterialPropertyBlock.CopySHCoefficientArraysFrom
- Texture 2D reference links to missing documentation
- [Search] Help (?) does not work as a Search Filter
- Quest apps lose head and controller tracking
Resolution Note:
Limitation of the Standalone Profiler when saving data.