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
- PlayerPrefs get corrupted when a minimized fullscreen Player is closed through the Taskbar
- "To Debug, run app with -diag-job-temp-memory-leak-validation cmd line argument. This will output the callstacks of the leaked allocations." warning is printed when JobTempMemoryLeakValidation switch is enabled
- Main Thread stalling when loading Audio Source asset asynchronously while preloading another Audio Source asset
- Material artifacts occur in the Material Preview window when baked lighting is applied to scenes
- Package Manager Filters (Status) dropdown is different color than Packages, Sort or Add package dropdowns
This is a duplicate of issue #941880