Search Issue Tracker
Fixed in 2020.1.X
Votes
0
Found in
2018.1.0f2
Issue ID
1058902
Regression
No
Crash at RendererScene::SceneAfterCullingOutputReady when entering playmode and using Vectrosity plugin to draw VectorLine
Crash happens when Draw3DAuto() function is called for the VectorLine which is set to Visibility.Static in the VectorManager.
Steps to reproduce:
1. Open "Galaxy" scene from "OpenSpaceOriginal.zip" project
2. Press Play
Reproducible with: 2018.4.19f1, 2018.1.9f1, 2018.2.2f1, 2018.3.3f1, 2019.1.b1, 2019.2.0a2
Note: Crash does not happens, if Pause button is pressed before entering Playmode, and then it's un-paused.
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
- "Shader warning in 'Hidden/Light2D': implicit truncation of vector type" is thrown when building Universal 2D template
- AI Assistant breaks compilation of packages using System.Runtime.CompilerServices.Unsafe via auto-referencing
- Unity Hub checks the "Documentation" module by default on the 6.4 and 6.5 streams despite that it was unchecked with the previous installs
- Shortcut that toggles between Dopesheet and Curves Views in the Animation Window's Timeline is mislabed
- Property List Items Overlap onto the Property List's top edge when scrolling through a long Property List
Resolution Note (fix version 2020.1):
Fixed in: 2020.1.0a22
The crash is caused by calling DestroyImmediate during the rendering call backs. An object is destroyed just before it is getting rendered. As it is destroyed there is nothing to render anymore. The editor will now throw a warning when attempting to DestroyImmediate during the rendering call backs. Destroy should be used instead.