Search Issue Tracker
Won't Fix
Votes
0
Found in
2023.1.0a1
2023.2.0a1
2023.3.0a3
6000.0.0b11
Issue ID
UUM-5764
Regression
No
Crash on ComponentMatchesRequirement_ByScriptingClassNoInterface when calling GameObject.Instantiate function
How to reproduce:
1. Open the user’s attached project
2. Open the "_StylizedTerrain" Scene
3. Enter the Play mode
4. Hold the R2 button on the controller until the biker crashes
5. Hold the Y button on the controller to call the “GameObject.Instantiate” function
6. Repeat step 5 a dozen times
Expected result: The Editor doesn’t crash
Actual result: The Editor crashes
Reproducible with: 2020.3.36f1, 2021.3.6f1, 2022.1.5f1, 2022.2.0a17, 2023.1
Could not test with: 2019.4.40f1 - due to errors in the Console window
Note:
- The issue was reproduced using the Xbox One controller
First lines of stack trace:
0x00007ff647250698 (Unity) ComponentMatchesRequirement_ByScriptingClassNoInterface
0x00007ff647250230 (Unity) GetComponentsOfTypeFromGameObject<1,0>
0x00007ff6472554b9 (Unity) ScriptingGetComponentsOfTypeFromGameObject
0x00007ff6472558c6 (Unity) ScriptingGetComponentsOfTypeFromGameObjectFastPath
0x00007ff64636c1b8 (Unity) GameObject_CUSTOM_TryGetComponentFastPath
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
- Rendering/Decal Layer Mask options are different inside Prefab Mode and outside Prefab Mode when the project is upgraded to Unity 6
- The Shortcuts window cannot be docked when it is invoked from the Shortcut Helper Bar
- Incorrect Realtime GI Light Probes baking when more than one Light Probe Group is used and "Baked Global Illumination" is enabled
- Hovering on the three-dot menu also highlights the tab header near it when not all tabs fit the bar
- Crash on PPtr<Object>::operator when undoing "Modern UI Pack" elements
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.