No, 64 bit seems fine in my initial test.
@mchaptel (mchaptel) This is currently a limitiation of 2D mode. We are working to try to solve it, but now you unique option to solve it is switch to 3D mode.
@Jacques Lucke (JacquesLucke) did you get the error in 64 bits version?
I'm investigating this. Right now I'm trying to figure out how to make a 32 bit debug build on windows that does not crash when I remove any object...
Thanks, I was able to reproduce it now.
Are you able to reproduce the issue in a new file still?
Created new report T62838
@Dont Want (McLP), please create a new bug report for your case.
This crash happens instantly on my system. No message in the console.
Thu, Mar 21
Wed, Mar 20
Tue, Mar 19
@Antonio Vazquez (antoniov), dependency graph operates in an evaluated domain, with all IDs being copied and decoupled from the original ones. The bakeModifier() does proper way of updating dependency graph for the new frame, but then it attempts to use original object to deform vertices.
That could work in some cases, because generally transformation matrices are copied back to original, but you should not rely on that.
Proper solution is to do all evaluation and deformation in the evaluated domain, and them copy things back (or, at least, pass all the evaluated datablocks to deformation and pass original data to be deformed).
Mon, Mar 18
@Sergey Sharybin (sergey) I don't know why it's not working the armature deform here.
This appears to be fixed.
I have not been able to reproduce this crash on Linux. There may be random memory corruption involved, or something with thread timing.
Sat, Mar 16
Crashed again, with a different console complaint this time:
@Antonio Vazquez (antoniov) will comment to confirm after this render is done, But on frame 1000 without problems so far.
@Brecht Van Lommel (brecht) What can we do here?
@Tomasz Kaye (bitbutter) I got an error with sound rendering your file. Are you sure we can close it?
Checking console log showed that it was a problem with a 3rd party add-on (snapscrubber). Removing the add on fixed the problem.
The crash is related to sound. Here the call stack:
Fri, Mar 15
Fixed with d5d518b96c16
@Antonio Vazquez (antoniov), I think clicking might as well activate the layer, same kind of activation happens for other types of items in the outliner.
Really, the Outliner is not designed to use as main point to change layers. There is panel for that and there, you only need a click and have more tools to manage layers.
Thu, Mar 14
Tested with Duet Display instead of Astropad. Same issue. So it seems not to be an issue with Astropad itself, but probably an issue in Blender itself.
I can confirm the issue here, using an iPad Pro as input: