hi there. We’ve been testing with blender 2.80.41 to check compatibility with our addon, it now seems that a segfault occurs with 100% reproducibility when running bpy.ops.ed.undo_push in background. This was not the case for 2.80.40.
Now, I’ve been told that running operators in background is not something that is supported. But we’ve been making use of it to support synchronising lots of computers data for distributed rendering. Now that undo push crashes the background processes, we have to remove support for users using undo. As you can imagine, thats a pretty big hit. We’ll be telling our users that they have to be ‘perfect’
So, would it be possible for blender 2.80 beta to be restored to not having a segfault when we use the bpy.ops.ed.undo related operators in background? Another and perhaps better solution might be to allow us to directly access the undo history and be able to push and seek through the history, setting the state to whatever undo epoch we feel like (currently possible using bpy.ops.ed.undo_history(item=undo_index).
So, we’d really like to know, if either of those two options (preferably the latter) can be achieved, or if there are any alternatives.