Page MenuHome

Autosaves cause crashes on Windows 10 almost every session
Closed, ResolvedPublic

Description

System Information
Operating system: Windows 10, 64-bit
Graphics card: 2 CUDA GPUs: Nvidia GTX 1080 8 gb ram, Nvidia GTX 1070 8 gb ram
CPU: AMD Ryzen 7 2700x 3.7GHz

Blender Version
Broken: Release candidate 1, 687f1df5dbe2

Short description of error

Hello wonderful Blender developers! I have been working extensively with latest Blender release versions and I have been experiencing crashes all the time and I was failing to identify the source of the bugs because they were seemingly extremely random. I have launched latest releases of Blender in debug mode and seem to get to the bottom of the problem. Autosave seems to be crashing blender whenever you're actively working on the model and editing it. A lot of the times (for me it's like 90% of the time) Blender is trying to austosave and store the save but Windows will randomly come up with EXCEPTION_ACCESS_VIOLATION error.

Here are some excerpts from the console:

Version 280 sub 20 date 2018-07-14 11:44 hash 27ba739fb79
Read blend: D:\002_3d_projects\000_Blender_Scenes\000_PORTFOLIO\000_MV_BRAND\MeshVoid_Robot\MeshVoid_Thin\MeshVoid_Robotv7.blend
read file D:\002_3d_projects\000_Blender_Scenes\000_PORTFOLIO\000_MV_BRAND\MeshVoid_Robot\MeshVoid_Thin\MeshVoid_Robotv7.blend

Version 280 sub 74 date 2019-07-18 10:55 hash 687f1df5dbe2

Skipping auto-save, modal operator running, retrying in ten seconds...
Memoryblock free: pointer not in memlist
Memoryblock free: pointer not in memlist
Memoryblock free: pointer not in memlist
Memoryblock Chunk buffer: double free
Memoryblock free: pointer not in memlist
Memoryblock free: pointer not in memlist
Memoryblock free: pointer not in memlist
Memoryblock Data from ME: double free
Memoryblock free: pointer not in memlist
Memoryblock free: pointer not in memlist
Error: Failed to read blend file '': Missing DNA block
Memoryblock free: pointer not in memlist
Memoryblock free: pointer not in memlist
Memoryblock free: pointer not in memlist
Memoryblock free: pointer not in memlist
Skipping auto-save, modal operator running, retrying in ten seconds...
redo_cb: operator redo Rotate
Skipping auto-save, modal operator running, retrying in ten seconds...
Memoryblock free: pointer not in memlist
Memoryblock Chunk buffer: double free
Memoryblock free: pointer not in memlist
Error: Failed to read blend file '': Missing DNA block
Memoryblock SceneStats: double free
Memoryblock free: pointer not in memlist
Memoryblock free: pointer not in memlist
Memoryblock Chunk buffer: double free
Memoryblock free: pointer not in memlist
Memoryblock free: pointer not in memlist
Memoryblock free: pointer not in memlist
Memoryblock free: pointer not in memlist
Memoryblock free: pointer not in memlist
Memoryblock Chunk buffer: double free
Memoryblock free: pointer not in memlist
Memoryblock free: pointer not in memlist
Memoryblock free: pointer not in memlist
Memoryblock free: pointer not in memlist
Error : EXCEPTION_ACCESS_VIOLATION
Address : 0x00007FF6EC972860
Module : c:\000_Blender\blender-2.80.0-git.687f1df5dbe2-windows64\blender.exe

It's really annoying bug, if I set my autosaves to every 2 minutes or 1 minute then I get crashes almost in 90 % of the cases with this error (EXCEPTION_ACCESS_VIOLATION) . And also my guess is that this problem is Windows specific, as I had the same problem running certain Python scripts that were dealing with saving blend files on the drive. Blender is trying to save file in a non-standard to Windows 10 way? Please help me get to the bottom of this I have to reload the same scene again and again when I work because of that and it hinders the progress.

Thank you!

Exact steps for others to reproduce the error
1 - Launch blender on WIndows 10 platform
2 - Set autosaves frequency to every minute
3 - Start quickly modifying the mesh
4 - Crash in 90-% of the cases during auto-save

Details

Type
Bug

Event Timeline

Have you tried reproducing this with Factory Settings loaded?

If you start with Factory Settings (then set auto-save to 1m) and the default scene and just start modeling on the cube can you get it to fail?

Have you run with auto-save turned off for enough time to be sure that there are no problems in that case?

Perhaps it's also possible that what's happening is that something else is corrupting your document and it's just the auto-save that trips over it.

I played around for 20m or so (also on Windows 10) without being able to reproduce it. Are there specific operations that you're doing frequently or that seem associated with the crash that I can try?

Have you tried reproducing this with Factory Settings loaded?
If you start with Factory Settings (then set auto-save to 1m) and the default scene and just start modeling on the cube can you get it to fail?
Have you run with auto-save turned off for enough time to be sure that there are no problems in that case?
Perhaps it's also possible that what's happening is that something else is corrupting your document and it's just the auto-save that trips over it.
I played around for 20m or so (also on Windows 10) without being able to reproduce it. Are there specific operations that you're doing frequently or that seem associated with the crash that I can try?

Hmmm, I think you might be right, I think it is related to setting. As I was unable to replicate the error with settings reset to factory defaults, I even tried turning on some of the addons and hotkeys that I use during modeling after doing factory reset to try and catch the same error, but I failed. But I get the same error even with addons turned off but without the reset to factory settings. It might be specific to certain settings in preferences? I don't know... I will test it out tomorrow more thoroughly.

Gavin Scott (Zoot) triaged this task as Needs Information from User priority.EditedJul 18 2019, 9:22 PM

Thanks. Also make sure any non-standard add-ons you're using are specified by their developers as being compatible with the 2.80 RC. I think the most likely cause of your issues might be a bad add-on. Though usually disabling them would remove the problem something might get left behind.

O-o-okay, I spent literally 6 hours today trying to understand the cause of crashes. I've been launching Blender with factory settings and without resetting them. Without resetting the setting to factory defaults I would get that pesky
Error : EXCEPTION_ACCESS_VIOLATION Address : 0x00007FF6ECDF2B2F messages 100-% during my attempts.

Notice it's always the same error message, always the same EXCEPTION_ACCESS_VIOLATION and address. Also it seems that it is super random and might not be related to autosaves at all? I can only speculate as of now, but it seems to be the same error over and over again, It can also be an error that can be provoked by the addons, that are trying to check the file system for some thumbnails or files (loads of addons use that functionality), it can be autosave related (not sure, probably not)?

Also I have replicated the bug ONCE after making the factory reset and turning ON officially supported addons like F2 and Dynamic_Context_Menu (the one that appears when you hit spacebar). I tried to replicate it again afterwards for the second time by turning these two on, but failed, and frankly I am too tired after 6 hours of tests...

I have been trying to understand which of the addons causes the problem, and I was turning them off one by one after each crash to exclude the culprit-addon. but I failed to do so. First I turned off Hardops - as this addon was pretty unstable it would also giving me very strange messages in the console like: Invalid clnors in this fan! Still got the same error and a crash. Then I turned off Boxcutter - same stuff. Then I turned off Machinetools - same result. Then I turned off MeshMachine - same result. Then I turned off other various addons - same error and a crash. Then I turned off ALL user enabled addons (I don't use that many apart from already mentioned ones) and would still get the same crash, even though there were no user enabled addons.

So it should be related to something far more deep than I initially thought. Also there's loads of reports on this tracker from Windows users regarding that EXCEPTION_ACCESS_VIOLATION errors appearing randomly on different occasions and upon asking other users that are using Blender on Linux it seems they've never encountered the same problems as Windows users did. My guess is that the problem is buried quite deep in Blender and the way it interacts with Windows OS.

Currently I can't use Blender stably for more than 10-15 minutes with several addons running, and I am incapable to understand the reason of these crashes. It is currently only possible for me to work for a long period of time with clean factory reset vanilla settings, but I assume Blender is not intended to be used with no addons at all...

I am attaching the full crash report from my console along with my comments of actions for each session here:

Maybe this can help someone to identify what is the problem here. I'm really clueless as of now and I don't know should I switch back to 2.79 and finish the job. I don't think I will be able to finish it using vanilla blender 2.8 it will be a real drag...

I made a clean install, nuked all settings and deleted every files from Users folder and remade all hotkeys from scratch. It took a while but it seems that RC2 version is working fine for me now with addons. I do experience crashes however, but very rarely and unable to reproduce the logic of those and it's relatively stable to work for quite a long time now. I guess this thread can be closed, as I can't understand the exact reason of those crashes happening previously, therefore cannot produce exact steps to replicate the bug, so that something could be done.