Search Issue Tracker
Won't Fix
Votes
0
Found in
2022.3.41f1
Issue ID
UUM-77273
Regression
No
"Profiler is not able to flush data to a file or socket and exceeded maximum amount allowed memory for buffering" warning is being thrown after starting profiling using the Standalone Profiler
How to reproduce:
1. Create a new project
2. Open Standalone Profiler (Window -> Analysis -> Profiler (Standalone Process))
3. Enter Play Mode in the Editor
4. Observe the console
Expected result: No Errors or Warnings appear
Actual result: Warnings about reaching maximum allowed memory for buffering are spammed
Reproducible with: 2022.3.41f1
Reproduced on: Windows 10
Note: Does not reproduce when Profiler is used in Editor
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
- TSS Inspector creates invalid Project Relative paths for USS references in packages when adding References via Inspector
- Screen Space Ambient Occlusion is not visible when the directional light intensity is 0.001 or lower with the Deferred Rendering Path selected
- Unlinking Unity project from cloud throws "DirectoryNotFoundException" errors when the Build Automation package is installed
- Numeric input field for “Prewarm Time” doesn’t fully display decimal values
- Sprite Editor Overlay Menu issues
Resolution Note:
Bug fixes for the Standalone Profiler are currently being treated as low priority because it's not widely used. The built-in Profiler can be used as a workaround. We've also tested this in 2023.3 and are not seeing this bug there either. If we see more reports of this we will investigate and re-open it.