This is not that common of an issue, but it happens – when searching for memory leaks, remember to check any cross-referenced objects. Cross-referenced objects are, well, just that, objects that need to reference each other. For example, when “ClassA” needs to know about “ClassB”, and “ClassB” needs to know about “ClassA”. Continue reading to see how this can cause memory leaks in your projects and how to use Xojo’s WeakRef to fix it.
Comments closed