Search Issue Tracker
Fixed in 2022.1.X
Fixed in 2019.4.X, 2020.3.X, 2021.1.X, 2021.2.X
Votes
2
Found in
2019.3.0f6
2019.4
2020.2.0a16
Issue ID
1314831
Regression
No
Crash on Texture2D::GetPixelBilinear when attempting to enter another Scene
How to reproduce:
1. Open the attached project "Game.zip" (In Google Drive)
2. Open Scene "_MainScene"
3. Press Play
4. Press the "Gig Poster" button
Expected result: Another Scene is loaded and no crash
Actual result: Editor crashes after a new Scene is loaded
Reproducible with: 2019.4.25f1, 2020.2.0a16
Not reproducible with: 2020.2.0a17, 2020.3.51, 2021.1.5f1. 2021.2.0a16
Can't test with: 2018.4.34f1 (errors in the Console)
Stacktrace:
at <unknown> <0xffffffff>
at (wrapper managed-to-native) UnityEngine.Texture2D.GetPixelBilinearImpl_Injected (UnityEngine.Texture2D,int,single,single,UnityEngine.Color&)
at UnityEngine.Texture2D.GetPixelBilinearImpl (int,single,single)
at UnityEngine.Texture2D.GetPixelBilinear (single,single)
at UnityEngine.UI.Image.IsRaycastLocationValid (UnityEngine.Vector2,UnityEngine.Camera)
at UnityEngine.UI.Graphic.Raycast (UnityEngine.Vector2,UnityEngine.Camera)
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
- Test Runner’s vertical scrollbar overlaps with the up and down arrows and upper toolbar tabs when the window is minimized
- The Input Field view is not updated when deleting lines of text
- The scrollbar does not respect empty lines in the Input Field
- “Texture Atlas Viewer“ button text overlaps another button when the UI Toolkit Debugger is narrowed
- Thresholds are no longer automatically calculated after deleting Motion fields in Blendtrees
Resolution Note (fix version 2022.1):
Fixed in 2022,1,0a5
Crash should now be replaced by an error
Resolution Note (fix version 2021.2):
Fixed in 2021.2.0b10
Resolution Note (fix version 2021.1):
Fixed in 2021.1.20f1
Resolution Note (fix version 2020.3):
Fixed in 2020.3.18f1
Resolution Note (fix version 2019.4):
Fixed in 2019.4.30f1