Page MenuHome

Blender 2.8 (various versions) crashes in GPU animation rendering (many card types), both eevee and cycles
Open, Needs Triage by DeveloperPublic

Description

Been having this for quite some time now, with various blender 2.8 beta versions, both on my office and home desktops: I start rendering the animation, it keeps rendering for a random length of time, few frames or few hundred frames, till blender shuts off as if nothing happened.
Cards and CPUs are all stock, I tested RAM stability and its OK
Memory capacity also is not exceeded.
This happens only on 2.8, both cycles and eevee,.. 2.79b renders happily, still model in it but it's like 50% slower and can't seem to live with those times anymore.

System Information
Operating system: Win. 10 (pro and home)
Graphics card: Vega 56 reference + RX480 8GB one PC and Vega56 on the other
(crash happens with both or one card rendering on the dual GPU system)
Both systems have ample amounts of RAM for what I do (16 and 24 GB)
CPUs are a core i7 and AMD 870K

Blender Version
Blender 2.8 , this has been happening for a few weeks now, I try almost daily the beta versions.
On previous blender/amd driver versions there was also a driver crash or system freeze occasionally. Now just shuts off.

Exact steps for others to reproduce the error
It does not look specific to a file; happens with all my projects, both saved in 2.8 and 2.79 and opened in 2.8. You hit render and wait for it to happen.

Details

Type
Bug

Event Timeline

Brecht Van Lommel (brecht) triaged this task as Needs Information from User priority.

Even if it happens in all your files, we still need to have one simple example .blend to reproduce the problem.

OK, after trying this and that I finally narrowed it down to a texture issue: For cycles I added a texture limit in the simplify panel and now it runs fine. In eevee, in scene/shadows panel I dialed the cascade size down to 512 px from 1024.

...crashes keep happening, although I get the recently famous white screen freeze now instead of blender just going out. Unfortunately all these files contain parts I can not disclose for now, the only thing I can do is replace part of the file,...hoping to still get the crashes...

Brand new Blender user here looking to dive in and found this thread for my crashes for animation.

I tried applying a texture limit for the render as suggested and it helped, but only a bit. Blender would usually lock up after 7 frames. With the texture limit it locked up at 36 frames.
Being new to this world I apologize for not knowing exactly what you would need to keep looking in to this. I'd be happy to send you whatever I can to help.

I guess I can start with system specs...
Windows 10 Home 64-bit
Intel i9-9990k
Nvidia RTX 2070
32 GB memory
Blender version 2.807d792976e100

I guess I can start with system specs...
Windows 10 Home 64-bit
Intel i9-9990k
Nvidia RTX 2070
32 GB memory
Blender version 2.807d792976e100

Hello and welcome!
Are you rendering in cycles or eevee?... not that there is any major difference in 2.8, it seems to crash with both, only eevee crashes seem totally random (sometimes it even finishes the video), while cycles seems more prone to crash within the first 50 frames.

I'm rendering in Cycles and it does regularly crash in the first 50 frames. Although I did start at frame 16 and made it all the way through 160 once. Once. *sigh*

I had the same problem last week. One of my files cashed at random while rendering in cycles. I tried rendering on CPU only but it crashed too. It was impossible to reproduce. Then with an older Beta version of Blender 2.8 it rendered.
I will have a look on it. I have to render a lot in the next weeks, maybe I can reproduce the problem or it is solved already.

Marin Myftiu (mm25) added a comment.EditedFeb 19 2019, 10:52 AM

I had the same problem last week. One of my files cashed at random while rendering in cycles. I tried rendering on CPU only but it crashed too. It was impossible to reproduce. Then with an older Beta version of Blender 2.8 it rendered.
I will have a look on it. I have to render a lot in the next weeks, maybe I can reproduce the problem or it is solved already.

I believe these crashes are quite frequent and have to do with the way blender handles gpu memory (the fact that they seem consistent through both amd and nvidia cards, of various generations means architecture or drivers have little to do with it).. I just hope they solve this for the 2.8 release.
Another thing I am finding out recently is that 2.79 also crashes in dual gpu renders before the memory limit is reached: I have 2 amd cards of 8 gb each, so it should be 8gb total,.. However when the memory goes above 4gb crashes start to happen.. looks like somehow, blender or the driver allocates about 4gb on each card and cant go past it.. render with only one card and the problem is gone... Can anyone try this on nvidia cards?

Jacques Lucke (JacquesLucke) raised the priority of this task from Needs Information from User to Needs Triage by Developer.Mar 11 2019, 12:47 PM

Not sure if this is still a problem for some people but I did make one change. I had the default folder for renders changed to another drive. When I switch it back to the tmp folder I rendered fine for a full 250 frames. Can't way for sure if it's related to the folder or because I was rendering less intensive projects or not.

For your information, I rendered lots of different sequences in cycles on many computers in our company during the last week. No crash during rendering.

Brecht Van Lommel (brecht) triaged this task as Needs Information from User priority.Mar 22 2019, 12:04 PM

We still need to have one example .blend to reproduce the problem.


Here's the blend I was using. Again, it appears that the problem comes when I change the default folder for renders to another drive. I've changed it back to the system tmp folder and and rendering without problem

Not sure if this is still a problem for some people but I did make one change. I had the default folder for renders changed to another drive. When I switch it back to the tmp folder I rendered fine for a full 250 frames. Can't way for sure if it's related to the folder or because I was rendering less intensive projects or not.

Thank you! It helped me! Tried different paths and video formats, nothing of it helped.
P.S. Using RTX 2060 with latest Creator Ready drivers, Windows 10 64bit, Ryzen 7 1700, 16 GB RAM, latest Blender 2.8 64bit, Eeevee render

Same issue here. And what is interesting is, when I change the thread from 4 (max) to 3, it significantly increase the amount of frame rendered before it crashed (around 2-4 times the number of frame). Using both CPU + GPU for rendering.

My system is:
Kubuntu 18.04
Intel Core i5 3570
DDR3 4 GB
NVIDIA GT 730 GDDR5 1 GB
Blender version: 2.80 Daily build (tried new build almost every week since february)

Marin Myftiu (mm25) added a comment.EditedApr 6 2019, 8:45 AM

Same issue here. And what is interesting is, when I change the thread from 4 (max) to 3, it significantly increase the amount of frame rendered before it crashed (around 2-4 times the number of frame). Using both CPU + GPU for rendering.
My system is:
Kubuntu 18.04
Intel Core i5 3570
DDR3 4 GB
NVIDIA GT 730 GDDR5 1 GB
Blender version: 2.80 Daily build (tried new build almost every week since february)

In your case 1 gb is a bit too low to render on gpu and crashes are to be expected more often. It is however a most likely a memory management issue, since more memory seems to make things better.
Dont know much about Linux, but in windows the "committed memory" increases substantially with each thread used.

After another testing with various settings I found another interesting thing. Somehow, when I set Render > Display Mode > Keep User Interface and using minimum layout (3D viewport, shader editor, and Outliner) EEVEE rendering perfectly fine (in ordinary setting it keeps crashing before 50 frames). I haven't tried this method with Cycles though.

PS. I'm using animation nodes in this testing, and somehow when I change the shader editor to animation nodes it keeps crashing when rendering.

Philipp Oeser (lichtwerk) raised the priority of this task from Needs Information from User to Needs Triage by Developer.Apr 24 2019, 10:56 AM

I can't reproduce this on my end with (Linux, AMD).

I've been trying to render animation using EEVEE with Blender 2.80 RC1 and RC2 and it keeps crashing. The Cycles seems to be fine though. My system is still the same as above. There is one occassion when EEVEE working using the following trick:

After another testing with various settings I found another interesting thing. Somehow, when I set Render > Display Mode > Keep User Interface and using minimum layout (3D viewport, shader editor, and Outliner) EEVEE rendering perfectly fine (in ordinary setting it keeps crashing before 50 frames). I haven't tried this method with Cycles though.
PS. I'm using animation nodes in this testing, and somehow when I change the shader editor to animation nodes it keeps crashing when rendering.

That was when I'm using blender-2.80-7ad21c3876c2-linux-glibc217-x86_64 (released on 11 or 12 July 2019).

I do not know if this is useful information.. having started Blender 2.8 RC3 on a command line with the -d option, this is the result on the random rendering animation crash for me:
Error : EXCEPTION_ACCESS_VIOLATION
Address : 0x00007FF7D8A937E4
Module : E:\blender-2.80rc3-windows64\blender.exe

This happend with either GPU or GPU+CPU(there is not a single image texture in the scene). I am currently trying to reproduce with CPU.. but that takes ages :)
(Quadro P5000 NV 431.02, 2x Xeon E5-2699v3)

Edit: rendering to an external hard drive.

I do not know if this is useful information.. having started Blender 2.8 RC3 on a command line with the -d option, this is the result on the random rendering animation crash for me:
Error : EXCEPTION_ACCESS_VIOLATION
Address : 0x00007FF7D8A937E4
Module : E:\blender-2.80rc3-windows64\blender.exe
This happend with either GPU or GPU+CPU(there is not a single image texture in the scene). I am currently trying to reproduce with CPU.. but that takes ages :)
(Quadro P5000 NV 431.02, 2x Xeon E5-2699v3)
Edit: rendering to an external hard drive.

I tried the same thing in Linux and it just show something like this:

Switching to fully guarded memory allocator.

Blender 2.80 (sub 75)
Build: 2019-07-29 17:17:04 Linux Release
argv[0] = ./blender
argv[1] = -d
/run/user/1000/gvfs/ non-existent directory
Read prefs: /home/radifar/.config/blender/2.80/config/userpref.blend
read file /home/radifar/.config/blender/2.80/config/startup.blend
Version 280 sub 54 date 2019-04-07 15:02 hash 75f551facaf0
found bundled python: /home/radifar/blender/blender-2.80-linux-glibc217-x86_64/2.80/python
Registered Animation Nodes
Read blend: /home/radifar/blender/Practice/collapsing-cube-eevee-02.blend
read file /home/radifar/blender/Practice/collapsing-cube-eevee-02.blend
Version 280 sub 61 date 2019-05-11 18:20 hash ebc44aae9897
Evaluate all animation - 1.000000
No Actions, so no animation needs to be evaluated...
Skipping auto-save, modal operator running, retrying in ten seconds...
Saved: '/home/radifar/Pictures/AN Collapsing Cube - EEVEE 720p/0001.png'
Time: 00:02.63 (Saving: 00:00.16)

Evaluate all animation - 2.000000
No Actions, so no animation needs to be evaluated...
Saved: '/home/radifar/Pictures/AN Collapsing Cube - EEVEE 720p/0002.png'
Time: 00:01.58 (Saving: 00:00.15)

Evaluate all animation - 3.000000
No Actions, so no animation needs to be evaluated...
Saved: '/home/radifar/Pictures/AN Collapsing Cube - EEVEE 720p/0003.png'
Time: 00:01.46 (Saving: 00:00.16)

Evaluate all animation - 4.000000
No Actions, so no animation needs to be evaluated...
Saved: '/home/radifar/Pictures/AN Collapsing Cube - EEVEE 720p/0004.png'
Time: 00:01.46 (Saving: 00:00.16)

Evaluate all animation - 5.000000
No Actions, so no animation needs to be evaluated...
Saved: '/home/radifar/Pictures/AN Collapsing Cube - EEVEE 720p/0005.png'
Time: 00:01.47 (Saving: 00:00.16)

Writing: /tmp/collapsing-cube-eevee-02.crash.txt
Writing: /tmp/collapsing-cube-eevee-02.crash.txt
Segmentation fault (core dumped)

So I tried the --verbose option, and when I'm trying to find explanation about verbosity I found this trick:

blender -b filename.blend -a > nul 2>&1

source: https://blenderartists.org/t/control-blender-verbosity-when-starting-from-command-line/607255/4

And it is working!