Search Issue Tracker

Active

Under Consideration for 6000.0.X, 6000.2.X, 6000.3.X, 6000.4.X

Votes

0

Found in

6000.0.59f1

6000.2.7f1

6000.3.0b4

6000.4.0a1

Issue ID

UUM-121642

Regression

Yes

Object.Destroy performs significantly worse compared to 2022.3

-

How to reproduce:
1. Extract the “IN-115094.zip → Build” archive
2. Open the Editor
3. Open the Command Prompt
4. Run the “ZR.exe” with the argument “-batchmode“ to launch the server
5. Run the “ZR.exe“ with the argument “-noPlatform“ to launch the client
6. When the client Player launches, hold the “2” key to skip the player customization
7. When in tutorial mode, press ESC and exit the tutorial (if you get stuck on the loading screen, exit the client (ALT+F4) and relaunch it)
8. Press “Custom Game“ on the left side, then press “Join“ to join a Custom Server
9. Join the active Lobby
10. Press the “/“ key and type in “add_bot 8“, then press Enter
11. Press the “/“ key and type in “skip_timer“, then press Enter
12. Focus on the Editor and open Window → Analysis → Profiler
13. Select the Player with port 50001 and enable recording
14. Observe the profiler

Expected result: CPU Usage is consistent and has no frequent spikes, and the Destroy calls take <1ms
Actual result: Spikes in the “CPU Usage” section appear, and the Destroy calls take >5ms and sometimes >50ms

Reproducible in: 6000.0.59f1, 6000.2.7f1, 6000.3.0b4, 6000.4.0a1
Not reproducible in: 2022.3.62f1
Could not test in: 2023.3.0a1 (project is too large to be downgraded)

Reproduced on: Windows 11 Pro (24H2)
Not reproduced on: No other environment tested

Notes:
- The user states that this does not reproduce in the Editor or in the 2022.3 stream (I could not test this locally)
- I am unable to create a smaller reproduction project, as it doesn’t guarantee the same behavior as the user’s project
- Downgrading to find the first regressed version is impractical and would take unreasonably long to find it, however there is a regression

Add comment

Log in to post comment