Timeline for Godot Array Reference Counting
Current License: CC BY-SA 4.0
4 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| May 4, 2024 at 15:18 | comment | added | Pikalek |
docs on basic mem management Godot implements reference counting to free certain instances that are no longer used, instead of a garbage collector, or requiring purely manual management. RefCounted things are freed automatically when not in use. Anything else will remain in memory until it is deleted with free() or queue_free().
|
|
| May 4, 2024 at 15:05 | comment | added | liggiorgio | It doesn't: non-reference counted, Engine-related things are either persistent (such as Servers) or handled internally. If you create non-reference counted entities, it's your responsibility to free the memory allocated (e.g. Nodes, Objects). | |
| May 4, 2024 at 14:31 | comment | added | DavidT |
For points 2-4 - If Godot is not reference counting how does it know when to free the memory (note: In the question I called out it's not related to the RefCounted class) but I don't know what Godot is doing if its not reference counting (the technique) to manage the memory?
|
|
| May 4, 2024 at 13:47 | history | answered | liggiorgio | CC BY-SA 4.0 |