Fix object copying not ensuring validity of material arrays.

Related to T56363, this is not fixing the root of the bug, but ID
copying should always be a good occasion to ensure sanity of our data
(and error checking is always better than a crash!).
This commit is contained in:
Bastien Montagne
2018-08-14 13:35:51 +02:00
parent 73234a9122
commit 932251caea

View File

@@ -1124,6 +1124,12 @@ void BKE_object_copy_data(Main *UNUSED(bmain), Object *ob_dst, const Object *ob_
ob_dst->matbits = MEM_dupallocN(ob_src->matbits); ob_dst->matbits = MEM_dupallocN(ob_src->matbits);
ob_dst->totcol = ob_src->totcol; ob_dst->totcol = ob_src->totcol;
} }
else if (ob_dst->mat != NULL || ob_dst->matbits != NULL) {
/* This shall not be needed, but better be safe than sorry. */
BLI_assert(!"Object copy: non-NULL material pointers with zero counter, should not happen.");
ob_dst->mat = NULL;
ob_dst->matbits = NULL;
}
if (ob_src->iuser) ob_dst->iuser = MEM_dupallocN(ob_src->iuser); if (ob_src->iuser) ob_dst->iuser = MEM_dupallocN(ob_src->iuser);