Search Issue Tracker
Fixed in 2019.1.X
Fixed in 2019.2.X
Votes
0
Found in
2019.1.1f1
2019.1.3f1
2019.2.0a1
2019.3.0a1
Issue ID
1163080
Regression
No
Crash on Material::SetFloat after calling Graphics.Blit()
How to reproduce:
1. Open the "Graphics_Blit_Crash.zip" project
2. Build the Crest/Crest-Examples/Main/Scenes/main.unity" scene
3. Run the build
Actual result: Unity crashes.
Reproducible with:2019.1.1f1, 2019.1.8f1, 2019.2.0b7, 2019.3.0a6.
Notes:
Can't test 2018.4 and earlier versions because Graphics.Blit(Texture source, RenderTexture dest, int sourceDepthSlice, int destDepthSlice) was implemented only in 2019.1.
The crash happens because of code "Graphics.Blit(Texture2D.blackTexture, _targets, -1, lodIdx);" LodDataMgrShadow.cs:186.
The Editor doesn't crash.
----------------------------
Fixed in 2019.3.0a8, 2019.2.0b9, 2019.1.10f1.
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- “[Worker0] Could not generate preview image“ error when opening macOS native plugin in the Inspector with Architecture to build for set to ARM 64-bit
- [iOS] Application.absoluteURL is empty on Awake/Start when opening via deep link with Splash Screen disabled
- Crash on MemoryManager::Deallocate when rapidly calling Addressables.LoadAssetAsync
- Crash on physx::shdfnd::atomicIncrement when adjusting values on a character controller component after entering Play mode in Prefab edit mode
- [Rendering Debugger] [NewInputSystem] Debug Overlays in Play mode throws InvalidOperationException when using New Input System
Add comment