Search Issue Tracker
Fixed in 2019.3.X
Fixed in 2018.4.X, 2019.1.X, 2019.2.X
Votes
0
Found in
2018.3.0a4
2018.3.13f1
2019.1.0a1
2019.2.0a1
Issue ID
1148335
Regression
Yes
[Metal] Calling FrameTimingManager.GetVSyncsPerSecond() crashes the Editor
How to reproduce:
1. Create a new Unity project
2. Import the tester-attached script(NewBehaviourScript.cs)
3. Attach the script onto any GameObject
4. Enter Play Mode
Expected result: the Editor does not crash
Actual result: the Editor crashes
Reproducible with: 2018.3.0a4, 2018.3.14f1, 2019.1.0f2, 2019.2.0a13
Not reproducible with: 2017.4.26f1, 2018.3.0a3
Notes:
Could not reproduce with OpenGLCore Graphics API
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Player build freezes after calling Application.Quit() when the scripting backend is set to IL2CPP
- Texture is not applied on a Custom Render Texture when a Cubemap is selected as the texture
- 2D light leaks through ShadowCaster2D when ShadowCaster2D components are disabled then re enabled at runtime in Player builds
- Unity Hub redirects to The Unity Roadmap when navigating to “Send Feedback” option
- UI Toolkit throws warning and fails to clear references when fields are not typed as UnityEngine.Object
Add comment