Search Issue Tracker
Fixed in 2020.1.X
Fixed in 2019.3.X
Votes
0
Found in
2017.4.0f1
2018.3.0a1
2018.3.8f1
2019.1.0a1
2019.2.0a1
Issue ID
1144824
Regression
No
CustomRenderTexture.Update() causes silent crash after dropping a Prefab into a Scene
Steps to reproduce:
1. Open User-supplied project ("ProjectorSimulator_SRP.zip")
2. Open "Sample" Scene
3. Drag 'VideoProjector' Asset located in Assets -> ProjectorSimulator into Hierarchy
Reproduced in: 2017.4.25f1, 2018.13.f1, 2019.1.0f2, 2019.2.0a11
Note: After the first crash occurs, when you open the project again, it will crash after 2 seconds.
The third time Unity will freeze upon opening.
The crash no longer happens after removing 'Light' Component from the VideoProjector -> Red/Grey, so I'm sending it to Lighting Grabbag
The Light component also has "HD Additional Light Data" and "Additional Shadow Data" Components attached, which are only removed along with the 'Light' Component.
Combined, they take more than a thousand lines, so I did not do much testing inside those scripts, if, however, such testing is needed, ping me on Slack.
-
shwhjw
Apr 23, 2019 16:46
I overcame this issue by ensuring the textures of the Graphics.CopyTexture function in CookieCreator.cs were a certain format. Crash was definitely caused by CopyTexture.
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
- NullReferenceException when setting 'isTextObjectScaleStatic' to false on a disabled TextMeshPro GameObject
- Shader Stripping Custom Options disappear when exiting Play mode without reloading Domain
- Decals do not get projected when 'Rendering Layer Mask' on a GameObject is 23rd Layer or above due to encoding/decoding issues
- Deriving from SearchContextAttribute doesn't always work
- Scripting API documentation is missing for macOS editor extensions
Resolution Note (fix version 2020.1):
We fixed the issue where outstanding updates for a CustomRenderTexture would trigger a crash of the Editor when that CustomRenderTexture got destroyed.
Resolution Note (fix version 2019.3):
We fixed the issue where outstanding updates for a CustomRenderTexture would trigger a crash of the Editor when that CustomRenderTexture got destroyed.