Search Issue Tracker
Fixed in 2023.2.0a10
Fixed in 2021.3.X, 2021.3.23f1, 2023.2.X
Votes
0
Found in
2021.3.16f1
Issue ID
UUM-29300
Regression
No
Release player is consuming InitializationProfilerStartFrameRegistrator in non-development mode
User-provided reproduction steps:
1. Install Superluminal
2. Open the project “IN_32317”
3. Build the project
4. Add the Superluminal DLL besides the Unity Player Executable. Just like explained here: https://www.superluminal.eu/docs/documentation.html#unity_support
5. Configure Superluminal as shown in the “superluminalConfig.png" image
6. From Superluminal, record a session of the built Player
7. Wait for the Superluminal capture to process, and search for "InitializationProfilerStartFrameRegistrator" in the "function Statistics" searcher
Expected result: nothing was found in the search
Actual result: result related to “InitializationProfilerStartFrameRegistrator” was found
Reproducible with: 2021.3.16f1
Reproducible on: Windows 11
More provided info:
We're seeing that "InitPlayerLoopCallbacks()::InitializationProfilerStartFrameRegistrator::Forward" is still consuming time in a non-development build.
We would like to still be able to use the ProfilerRecorder to gather some performance data in some of our non-dev builds, but it should be disabled in the builds that we will ship.
Note: CQA couldn’t reproduce this issue
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Uninitialized variable warning appears in the Inspector of a custom shader when the variable is initialized
- "Failed creating toolbar element from ID..." error is thrown when resetting the Scene view Overlay layout while an Asset Transformer Toolbox overlay is active
- Entity ID for Font Assets is serialized twice which throws an error when using Debug Inspector
- Play Mode can be entered when disabling Adaptive Performance and pressing either the Play Mode button or the keyboard shortcut to enter Play Mode before recompilation leading to errors and warnings thrown
- Parent ListView element also becomes selected when inner ListView element is selected
Add comment