Search Issue Tracker
Fixed
Fixed in 6000.3.6f1, 6000.4.0b6, 6000.5.0a6
Votes
0
Found in
6000.3.0a5
6000.4.0a1
6000.5.0a1
Issue ID
UUM-132091
Regression
No
2D Physics callback targets should have doc information about the GC and assigned objects.
As per the discussion here, assigning a System.Object that isn't a UnityEngine.Object will not keep the object alive and away from the GC.
This is because we use a weak-reference as lazy-resets to keep performance high.
We do not want to sacrifice performance so for this specific use-case and likely a niche problem, we should add information to all the "callbackTarget" scripting docs.
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
- [UWP] Mouse movement re-triggers stale <Mouse>/scroll value after the scroll wheel is used once
- "Shutdown worker was forced killed because it kept running. Worker ..." errors are thrown after building a blank HDRP project
- [UI Toolkit] USS materials in AssetBundles break due to InstanceID referencing a material that no longer exists when a Scene is loaded through Addressables for the second time
- Help button leads to a missing documentation page when clicked on a Font Import Settings in the Inspector
- TextMeshPro Text Component reads bottom-to-top instead of top-to-bottom when using RTL Editor
Resolution Note:
Fixed in 6000.5.0a6
Resolution Note (fix version 6000.5.0a6):
Fixed in 6000.5.0a6
Resolution Note (fix version 6000.4.0b6):
Fixed in 6000.4.0b6
Resolution Note (fix version 6000.3.6f1):
Fixed in 6000.3.6f1