Search Issue Tracker
Fixed in 7.2.0
Votes
0
Found in [Package]
2018.4
2019.2.17f1
2020.1
Issue ID
1206823
Regression
No
Crash on FlareManager::Update when Flare Layer is added to a GameObject and then removed
Steps to reproduce:
1. Create a new HDRP project or open an existing one
2. Create an empty GameObject in any Scene
3. Add a "Flare Layer" component
4. Remove the "Camera" component added together with the "Flare Layer"
5. Remove the "Flare Layer component"
Reproducible with: 2018.4.15f1, 2019.2.18f1, 2019.3.0f5, 2020.1.0a19 (HDRP 1.1.1, 4.1.0, 4.10.0, 6.9.0, 6.9.2, 7.1.7)
HDRP not available in 2017.4
First 5 lines of the stacktrace:
0x00007FF7B5C6D865 (Unity) FlareManager::Update
0x00007FF7B5C67232 (Unity) FlareManager::RenderFlares
0x00007FF7B5C8D93C (Unity) Camera::RenderLensFlares
0x00007FF7B5C843A3 (Unity) Camera::DoRenderPostLayers
0x00007FF7B50A4B99 (Unity) Camera::DoRenderGridAndPostLayers
Notes:
- Does not reproduce with the built-in renderer, "Can't remove component" error window is shown when trying to remove "Camera" component
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Too little validation messages in the "WebAssembly Language Features" Memory settings
- Project Settings Search Highlights are misaligned when using the Bitmap Text Rendering Mode
- "GetControlID at event ValidateCommand returns a controlID different from the one in Layout event" Warning is thrown when undoing the deletion of Sprite Shape Profile
- Memory related fields in the "WebAssembly Language Features" can be set to the negative numbers
- "WebAssembly Language Features" Header in the Player Settings has a smaller indentation
Add comment