Search Issue Tracker


Fixed in 2021.3.23f1, 2023.2.0a10



Found in


Issue ID




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: [|]
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

Add comment

Log in to post comment