CustomDataLayer with type CD_MLOOPUV in Mesh::ldata::layers sometimes points to different memory than Mesh::mloopuv, even when only one set of uv coordinates is present. The data pointer in the layer sometimes changes from null to an adress when making slight changes (to irrelevant objects in the file) and resaving the file.
this wasn't the case in 2.74 and earlier where the pointers where always equal.
Psy-Fi mentioned that this data should be the same also.
<psy-fi> hmmm...it's possible that there was some confusion with the recent looptriangle commit
<psy-fi> in any case, they should be the same