Search Issue Tracker
Won't Fix
Under Consideration for 2021.3.X, 2022.3.X, 6000.0.X, 6000.1.X
Votes
0
Found in
2021.3.31f1
2022.3.11f1
2023.1.17f1
2023.2.0b14
2023.3.0a11
6000.0.0b11
6000.1.0a7
7000.0.0a1
Issue ID
UUM-53886
Regression
No
Private array loses references when the GameObject is marked as DontDestroyOnLoad
Reproduction steps:
1. Open the "IN-50710.zip" project
2. Open the "Assets/Startup" Scene
3. Attach a debugger to the project
4. Set breakpoints in lines 38 and 66 of the "Assets/Scripts/Controllers/CameraController.cs" Script
5. Enter Play mode
6. Resume the program until the breakpoint in line 38 is hit
7. Observe the "players" field of the "CameraController" Script
8. Resume the program and observe the "players" field again
Expected results: The "players" field has the "Tom" GameObject
Actual results: The "players" field has a "null" value
Reproducible with: 2021.3.31f1, 2022.3.11f1, 2023.1.17f1, 2023.2.0b14, 2023.3.0a11
Reproducible on: macOS 14.0 (M1)
Not reproducible on: No other environment tested
Note: Reproducible in Standalone Player
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
- SIGSEGV error when adding EditorApplication.delayCall callback declared in complex generic type and exiting Unity in `Performanc
- Resize cursor does not appear while approaching window edge from inside the player window when using Input System as the Input Handler
- IMGUI Debugger Instructions are flickering when the Inspected View is set to Scene and mouse cursor is moved over the Scene View
- [Windows] “GUI Window tried to begin rendering while something else had not finished rendering!…” Error is thrown after opening “Insert a template into current VFX Asset” window
- No InvalidOperationException error thrown when Active Input Handling is set to "Input System package" and "OnMouseDown()" is triggered
Resolution Note:
Thank you for reporting a bug to Unity.
We have reviewed the issue carefully, and in this case, the team is unable to prioritize fixing this bug. There are a number of reasons we make this decision, including the impact and severity of the issue across our user and customer base, and the possibility that future plans may solve the problem in a different way, or that a workaround for the bug may be available.
Today we will be closing this case. Thank you again for taking the time to report this issue, and please let us know if there is anything else that changes the impact or severity of this issue.