Search Issue Tracker
Fixed in 2018.3.X
Destroying trigger colliders takes longer than without trigger
1. Open the attached project
2. Open scene "scene"
(use the GUI for the steps below)
4. Choose the amount of objects, spawn them and then destroy them
5. Notice the console output
6. Now select the flag "Create triggers?" and repeat step 4
7. Notice the editor freeze and console output
Expected result: Time destroying objects with colliders that are with and without "Is trigger" flag checked should be about the same.
Actual result: Destroying objects with trigger colliders takes significantly more time than destroying objects with simple colliders.
Test results: destroying 4000 trigger colliders takes 2100ms while destroying same amount of simple colliders takes 400ms
Reproduced on: 5.2.4f1, 5.3.3p2, 5.4.0b8
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
- Light brightness gets intense until the 'Lightmap Encoding' quality is changed when baking Lightmap
- Crash on LinearCollectionField::LinearCollectionField after a 'm_ArrayField != SCRIPTING_NULL' assertion when opening a project
- Import Activity Window takes long time to open
- [Android] Artifacts appear in texture Preview Window on Android Platform when selected Override ETC2 fallback is 16-bit
- Child Canvas' Sorting Layer is changed to the same value as the parent Canvas after interacting with Dropdown UI object