If do this steps multiple time on single object, crash is there even in 3.4.
I can reproduce this and also memory leak is there in 3.5/3.4 versions.
We can not added backward compatibility here. We've changed the socket name, so this probably won't work now.
Operating system: Windows-10-10.0.19045-SP0 64 Bits Graphics card: NVIDIA GeForce GTX 1060 6GB/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 527.56
Thanks for the report.
While we want to improve Blender to handle system running out of memory gracefully, this is not currently considered a bug.
Thanks for the report. While we do continue to work on improving performance in general, potential performance improvements are not handled as bug reports.
To improve performance, consider…
This happens only for object move gizmo operator, or you can reproduce this for any other?
- Move nodes in node editor.
- Change bevel size in edit mode.
- Align lamp on other object.
- ... .
Not sure. Also, can you check if you have any third party addons installed? Maybe an antivirus?
Hm. Can you make sure you have the latest drivers installed now?
Potentially duplicate of blender/blender#108202
Can you start blender from terminal with --debug-depsgraph-no-threads --threads 1
flags?