Was actually harmeless and not crashing, but I'd say more or less only by luck: the NULL-check for region data would only evaluate to true for the correct 3D View region. However, if we were to add region data to a different region type in future, this would lead to undefined behavior if executed in the wrong region.