Page MenuHome

"Fix T84049: Crash when using Cycles Progressive Refine with OptiX+CPU" actually causes hybrid rendering to crash
Closed, ResolvedPublic

Description

System Information
Operating system: Linux-5.8.0-40-generic-x86_64-with-debian-bullseye-sid 64 Bits
Graphics card: GeForce GTX 1080 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 460.32.03

Blender Version
Broken: version: 2.93.0 Alpha, branch: master, commit date: 2021-01-20 15:35, hash: rBe12eb89f22c6
Worked: all 2.93 versions before commit 4a09907eab2a

Short description of error
F12 rendering anything with CUDA+CPU instantly crashes Blender or stops the rendering and throws a CUDA error

Exact steps for others to reproduce the error

  • Open Blender / default cube or anything else
  • Configure Blender to use CUDA with both GPU and CPU enabled (Edit > Preferences > System)
  • Enable View Layer Properties > Passes > Data > Denoising Data
  • Press F12
  • Crash or CUDA error

Event Timeline

I'm unable to reproduce the issue, but maybe that's not surprising since I also couldn't reproduce T84049.

Invalid value in cuMemFree(mem.device_pointer) (device_cuda_impl.cpp:970)
Launch failed in cuMemcpyDtoH( (char *)mem.host_pointer + offset, (CUdeviceptr)mem.device_pointer + offset, size) (device_cuda_impl.cpp:1034)

Hi. I cannot reproduce in latest Blender from master built by myself ( Linux, Nvidia 460.32.03, Blender c07c110467ca, OptiX 7.2.0)
But maybe I'm confused with the steps you mention. Title says Optix+CPU and description CUDA+CPU. Anyway here it works with CUDA or OptiX and Progressive Refine in my tests.

Thanks for testing YAFU. I don't mean progressive refine but normal tiled rendering with GPU+CPU (CUDA+CPU).
The OptiX and progressive part of that bug report comes from the commit that caused the crashes for me ;)
I also build with OptiX 7.2.0

Oh I understand. But no, I can't make it crash here. Using CUDA V10.1.105 to build.

Hmm, I'm using CUDA 11.2 on my side. Maybe that's the problem.

OK, a quick update:

I tried several things and after renaming the startup.blend file I could render properly. I think I found the cause:
In my startup.blend I activated "Denoising Data" pass by default because I always use it in compositing afterwards. As soon as I unchecked this pass the rendering was working properly again.

So if someone tries to reproduce this, please also switch the "Denoising Data" pass on!

And just to confirm I just downloaded today's Buildbot build and it fails the same way as my own build yesterday. So it's not a CUDA 10 vs 11 thing. ( blender-2.93.0-41a945d7469f-linux64 )

Robert Guetzkow (rjg) changed the task status from Needs Triage to Confirmed.Jan 21 2021, 12:34 PM
Robert Guetzkow (rjg) updated the task description. (Show Details)
Robert Guetzkow (rjg) updated the task description. (Show Details)
Robert Guetzkow (rjg) updated the task description. (Show Details)

Ah, that's right, with Denoising Data here hybrid render with default cube does not finish, it hangs and I can't cancel render either.

This is why it is important to share a .blend file no matter how simple the steps are to reproduce the problem :)

Yeah, right! At first it looked too easy because I didn't notice that Denoising Data was enabled and I could easily reproduce it with an empty scene file (which I assumed was a bit stupid to upload). But in the end it would've helped.