Closed VascoPi closed 1 year ago
It's interesting that this would fix the problem, or rather that the different order only effects one platform.
@VascoPi can you explain WHY this fixed it? Not clear to me?
While debugging it was found that utilizing bpy.utils.register_classes_factory
's order for given classes causes the error.
Simply changing the unregistering order fixes the issue.
Eventually, I didn't find an accurate explanation for why it happens only at M2. Looks like the blender code doesn't have a special condition for M2 as well.
Also changing Python version to 3.10 while the building process doesn't give any results.
Agree it's strange behavior on M2 because no warnings or errors are observed on other systems using the common bpy.utils.register_classes_factory
's order for given classes.
PURPOSE
Mac Mini M2 crash on addon deactivation. https://github.com/GPUOpen-LibrariesAndSDKs/RadeonProRenderBlenderAddon/issues/626
EFFECT OF CHANGE
Fixed addon deactivation crash on Mac Mini M2.
TECHNICAL STEPS
Put apart un/registration for node, socket, and socket interface classes and changed its order.