Search Issue Tracker

Active

Under Consideration for 2021.3.X, 2022.3.X, 6000.0.X

Votes

1

Found in

2021.3.45f1

2022.3.50f1

6000.0.23f1

6000.1.0a7

Issue ID

UUM-84430

Regression

No

EnlightenRuntimeManager.SyncRuntimeData has huge time usage when unloading an active Scene

--

-

Reproduction steps:
1. Open the attached “BugRepro” project
2. Open the “Assets/Scenes/Base” Scene
3. In the Profiler window (Window > Analysis > Profiler), set the profiling target to Edit Mode and start recording
5. Enter Play Mode
6. Wait 5 seconds for a second Scene to start loading, then wait 5 seconds for the second Scene to start unloading
7. After the second Scene has finished unloading, stop the recording in the Profiler window
8. In the Profiler window’s CPU usage module, select the highest usage spike
9. In the module details panel’s search box, enter “EnlightenRuntimeManager.SyncRuntimeData“
10. Select the “EnlightenRuntimeManager.SyncRuntimeData” function and observe its “Time ms” value

Expected result: The recorded value should be small and insignificant
Actual result: The recorded value is 94939.97 ms

Reproducible with: 2021.3.45f1, 2022.3.50f1, 6000.0.23f1

Reproducible on: Windows 11
Not reproducible on: No other environments tested

Notes:
- In 6000.0.23f1, the Profiler will produce errors in step 6 which pauses the Play Mode, so to continue you need to unpause the Play Mode
- In 6000.0.23f1, the recorded value is smaller, ranging from 25000-50000 ms
- The recorded values may differ across different hardware specification

Add comment

Log in to post comment

All about bugs

View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.