Fix inaccuracies in the report of leaked objects
This commit is contained in:
parent
26b1fd0d84
commit
a04a67ead6
1 changed files with 3 additions and 2 deletions
|
@ -2222,8 +2222,9 @@ void ObjectDB::cleanup() {
|
||||||
extra_info = " - Resource path: " + String(resource_get_path->call(obj, nullptr, 0, call_error));
|
extra_info = " - Resource path: " + String(resource_get_path->call(obj, nullptr, 0, call_error));
|
||||||
}
|
}
|
||||||
|
|
||||||
uint64_t id = uint64_t(i) | (uint64_t(object_slots[i].validator) << OBJECTDB_VALIDATOR_BITS) | (object_slots[i].is_ref_counted ? OBJECTDB_REFERENCE_BIT : 0);
|
uint64_t id = uint64_t(i) | (uint64_t(object_slots[i].validator) << OBJECTDB_SLOT_MAX_COUNT_BITS) | (object_slots[i].is_ref_counted ? OBJECTDB_REFERENCE_BIT : 0);
|
||||||
print_line("Leaked instance: " + String(obj->get_class()) + ":" + itos(id) + extra_info);
|
DEV_ASSERT(id == (uint64_t)obj->get_instance_id()); // We could just use the id from the object, but this check may help catching memory corruption catastrophes.
|
||||||
|
print_line("Leaked instance: " + String(obj->get_class()) + ":" + uitos(id) + extra_info);
|
||||||
|
|
||||||
count--;
|
count--;
|
||||||
}
|
}
|
||||||
|
|
Loading…
Reference in a new issue