Page MenuHome

Cycles combined CPU + GPU render crash
Closed, ResolvedPublic

Description

System Information
Operating system: Windows 10
Graphics card: 2x GTX 1080ti

Blender Version
Broken: 2.80 Beta, 26d5a3625ed, 2018-11-29
Worked in: Every other 2.8 version in the last few months.

My cycles compute device is set to CUDA. I have the following selected for render:
GeForce GTX 1080 Ti
GeForce GTX 1080 Ti
Intel Core i0-7980XE CPU
Render device is set to GPU Compute.

Every time I hit render, the program crashes. This is true for both older 2.8 files, as well as brand new files created within the Beta. I cannot render single frames, or animations. The view port render preview still works. Rendering using CPU as the render device works, but crashes as soon as the render is complete. I have tested with 3 different blend files, and even tried rendering the default cube in a new blend file. It crashes ever time.

Exact steps for others to reproduce the error

Start new file
Set the render device to GPU compute
In the preferences, under general, select CUDA as the cycles compute device.
Select both Geforce GTX 1080 Ti cards,
Select the intel core CPU.
Save preferences
Press F12 to Render
System crashes immediately.

Event Timeline

OK, I think I'm onto something! :)

I also noticed that all of a sudden my own compiles both of Master and 2.80 started crashing (didn't render anything the last few days so I just noticed it some hours ago after the Beta release).
They only crashed if I used hybrid GPU and CPU rendering. GPU on its own rendered without problems, so did CPU only. My system is a Threadripper x2950 with a 1080ti running Linux Mint 19 BTW.

At first I thought it was my system or compiles but after downloading today's Beta it also crashed in the very same way. So I began investigating and during the last few hours I compiled several older versions of both Master and 2.80 until I found the point where both of them started to break. It's this last-minute-before-beta commit by Stefan Werner: https://developer.blender.org/rB7fa6f72084b1364cddfbef4f06bbb244210d6967 (Cycles: Add sample-based runtime profiler that measures time spent in various parts of the CPU kernel). All builds after that fail, all before run smoothly.

I hope that it can be fixed ASAP and a new Beta can be uploaded before the whole Blender 2.80 world bursts in flames... (just kidding, I just think it could stir up some dirt, there are several GPU related crash reports like this one already coming in).

Brecht Van Lommel (brecht) renamed this task from Blender Crashes when initiating cycles GPU render (tested on multiple 2.8 files.) to Cycles combined CPU + GPU render crash.Nov 29 2018, 10:57 PM
This comment was removed by Riley Brown (RileyBrown).

Sorry, can't confirm your other crash problem

Now it's better and I can render once crashing scene, but if I increase texture size it will show buckets on renderframe and then crash

Maybe it's related to memory limitations? But isn't Cycles supposed to load resources in RAM if there's not enough VRAM left?

63150511a29 also crashing this time, but render gets a bit farther.

@Bohdan Lvov (ostapblender), that sounds like a different issue, to be handled in a new report.

The same scene which yesterday would crash is now rendering fine. :)