Search Issue Tracker
Won't Fix
Under Consideration for 2022.3.X
Votes
0
Found in
2022.3.29f1
Issue ID
UUM-71734
Regression
Yes
Warnings are thrown when entering play mode with standalone profiler open
Steps to reproduce:
- Create a new project
- Open the Standalone Profiler (Window > Analysis > Profiler (Standalone process))
- Enter Play mode
Expected results: No warnings are thrown
Actual results: Warnings are thrown:
{code:java}
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 536887296 bytes while Profiler.maxUsedMemory is 536870912 bytes.{code}
Reproducible with: 2022.3.23f1, 2022.3.60f1
Not Reproducible with: 2022.3.22f1, 6000.0.40f1, 6000.1.0b9, 6000.2.0a6
Tested on (OS): Windows 10, Window 11
Note: At the time of reporting, the system had used ~50% of its Memory.
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
- TextMeshPro text input's caret is flickering when Line Mode is set to Multi Line and text is selected
- Can’t delete gradient keys with Mac keyboard or context menu options
- Editor freezes for a few minutes when closing or switching a VFX window that was opened in a previous project
- UI Overlaps when switching Render Pipeline Asset for different Quality Levels in Quality Project Settings
- Ray Tracing Shader link to the documentation isn’t working
Resolution Note:
Closing this because the fix is potentially risky to land in 2022 at this point in it's life cycle and we have not seen the problem in 6.0 or later.
Recommended workaround: if this is causing problems there are several possible workarounds; starting a separate Editor to connect and profile from, profiling from a separate machine, profiling a standalone player, or using other profiling tools (e.g. Samply).