Search Issue Tracker
Active
Under Consideration for 6000.0.X, 6000.2.X, 6000.3.X, 6000.4.X
Votes
2
Found in
6000.0.58f1
6000.2.6f1
6000.3.0b4
6000.4.0a1
6000.5.0a1
Issue ID
UUM-121369
Regression
No
MissingReferenceException occurs when entering Play mode with a locked GameObject in the Inspector
Reproduction steps:
0. Make sure your Enter Play Mode Settings are set to "Reload Domain and Scene", no other mode reproduces the issue.
1. Create a new Unity project
2. Create a new empty MonoBehaviour script
3. Add a GameObject to the scene
4. Add the MonoBehaviour (from Step 2) to the GameObject (from Step 3)
5. Add a Collider (e.g., BoxCollider) to the same GameObject
6. Lock the GameObject in the Inspector, by clicking on the padlock icon in the top-right corner of the Inspector
7. Enter the Play Mode
8. Observe the Console
Expected result: No errors occur
Actual result: "MissingReferenceException: The object of type 'NewMonoBehaviourScript' has been destroyed but you are still trying to access it." error is thrown
Reproducible with: 6000.0.58f2, 6000.2.6f2, 6000.3.0b4, 6000.4.0a1
Reproducible on: M1 Max macOS 15.6.1 (Tested by CQA)
Not reproducible on: No other environment tested
Comments (2)
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
- URP Realtime reflection probes do not update when RenderProbe() is being called once per second
- Addressable terrain shader variants are stripped from the Player
- [iOS] Debug.Log() appears as <private> in Console app
- UI stays in the background when it is disabled in simulator
- A wrong log file is attached when project is launched with a "-logFile" command line argument
NultraStudio
Oct 12, 2025 21:11
I am having the same issue on 6000.2.6f2 on Windows 11. If there is another unlocked inspector, or another inspector locked on a gameobject with no scripts, there are no issues.
Coniix
Oct 11, 2025 10:39
Also experiencing this issue in 6000.0.59f2 and on Windows 10