Search Issue Tracker
Duplicate
Votes
0
Found in
2018.2.0f2
Issue ID
1087422
Regression
No
Functions inside destroyed components can get called
How to reproduce:
1. Open the "Destroyed_call_repro.zip"
2. Open the "SampleScene.Unity" scene
3. Enter Play mode
4. Press A (Debug log called from Test.DoWork())
5. Press B (the Test game object is Destroyed)
6. Press A (Debug log is still called from Test.DoWork())
Actual result: Function attached to null GameObject gets executed.
Expected result: Function shouldn't get executed when the script is null.
Reproducible with: 2019.1.0a7, 2018.3.0b8, 2018.2.14f1, 2018.1.9f2, 2017.4.13f1.
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
- Keywords on Material Variants aren't automatically saved when changed on original Material through Shader Graph
- Light Probes get baked when calling LightProbes.Tetrahedralize
- Shadows flicker and cause visual artifacts when modifying a GameObject's bounds using Swizzle (Y Mask) and Sine Time nodes
- [WebGL] Frame rate drops by 5-20 fps when moving cursor or touch input in the Player
- Light bleeds when using box shaped spotlight with specific Emission Range values
This is a duplicate of issue #941880