Search Issue Tracker
Won't Fix
Won't Fix in 2023.3.X
Votes
0
Found in
2022.2.11f1
2023.1.0b8
2023.2.0a6
2023.3.0a3
Issue ID
UUM-29586
Regression
No
Crash on Component_Get_Custom_PropGameObject when selecting a script file
Reproduction steps:
1. Open the attached “CrashRepro” project
2. In the Project window, select “Assets/PlayerActions.inputactions”
3. In the Inspector window, click the Script selecting button
4. Search for “PlayerInput” and click on it
Expected result: PlayerInput is selected
Actual result: Unity Editor crashes
Reproducible with: 2022.2.0a15, 2022.2.11f1, 2023.1.0b8, 2023.2.0a6
Couldn’t test with: 2020.3.45f1, 2021.3.19f1, 2022.2.0a1 - 2022.2.0a14 (Input System 1.5.0 is working properly and I couldn’t find another way to select the Script File)
Reproducible on: Ubuntu 22.04, Windows 10 Pro 22H2
First lines of the stack trace:
0x00007ff72344dbc7 (Unity) Component_Get_Custom_PropGameObject
0x000001c3f56e1141 (Mono JIT Code) (wrapper managed-to-native) UnityEngine.Component:get_gameObject (UnityEngine.Component)
0x000001c29864c57b (Mono JIT Code) UnityEditor.SceneView:CallOnPreSceneGUI ()
0x000001c29864c3fb (Mono JIT Code) UnityEditor.SceneView:DoOnPreSceneGUICallbacks (UnityEngine.Rect)
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
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
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.
Resolution Note (2023.3.X):
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.