Search Issue Tracker
Fixed in 2017.1.X
Votes
0
Found in
5.6.0f3
Issue ID
897665
Regression
Yes
DestroyImmediate(RenderTexture) and creating and setting a new one in OnPreRender results in a crash
Steps to reproduce:
1. Create a new project
2. Import the attached script "TestScript.cs"
3. Add the script to a camera
4. Enter Playmode
Result: crash
Reproduced on 5.6.0a1, 5.6.0f3, 2017.1.0a5
Not reproduced on 5.5.3f1
Notes:
-Does not appear to crash on Standalone build
-Workaround: use Destroy(RenderTexture) instead
The workaround in current project(with SpriteLightKit)
1. Deleting Library folder from your project
2. Go to your project Assets folder ---> SpriteLightKit folder
3. Open SpriteLightKit.cs and change UnityEngine.Object.DestroyImmediate( _texture ); to UnityEngine.Object.Destroy( _texture ); on line 149
Verified FIXED 2017.1.0b6, 5.6.1p2
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- [Linux] Touch freezes in Player when any mouse button is clicked
- UnityEngine.Rendering.Volume.OnEnable() is called twice before OnDisable() creating multiple copies of the same volume when a volume is enabled right after Domain Reload when entering Play Mode
- Hinge Joint transforms are reset when toggling the "useMotor" property
- Motion Vector texture reports incorrect Mesh data when Mesh is coming from off-screen
- [macOS] Display flickers with bright colors when built Player uses 2 or more Displays
Add comment