Search Issue Tracker
Active
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 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.29f1
*Not Reproducible with:* 2022.3.22f1
*Tested on (OS):* Windows 10
*Note:* At the time of reporting, the system had used ~50% of its Memory.
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- An emoji is not shown in the UI Builder Viewport and the Game view when it is placed in the Labels text attribute and Usage Hints is set to Dynamic Color
- The Sprite Renderers are looking for Secondary Textures from the wrong page within the Sprite Atlas when the Sprite Atlas has a large amount of textures for packing
- [URP] Invalid update of shader stripping settings
- [HDRP] Errors on Shader stripper that do not stripp shaders.
- Usage of Adaptive Probe Volumes throws a lot of IndexOutOfRangeException and Assertion Failed errors
Add comment