Page MenuHome

Cycles CUDA Illegal Address when unhiding an object with volumetric material
Closed, DuplicatePublicBUG

Description

System Information
Operating system: Linux-5.10.0-6-amd64-x86_64-with-glibc2.31 64 Bits
Graphics card: GeForce GTX 1070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 460.73.01

Blender Version
Broken: version: 3.0.0 Alpha, branch: master, commit date: 2021-09-22 07:47, hash: rB90b485845caf
Worked: before Cycles X was merged

Short description of error
Cycles produces the following error if a volumetric object is introduced into the scene by unhiding it while being in viewport rendered mode:

Illegal address in cuMemcpyDtoHAsync( mem.host_pointer, (CUdeviceptr)mem.device_pointer, mem.memory_size(), cuda_stream_)(intern/cycles/device/cuda/queue.cpp:207)

Exact steps for others to reproduce the error
This bug can easily be reproduced from the default startup file:

  1. assign a purely volumetric material to the default cube (either Volume Scatter or Volume Absorption)
  2. hide the cube
  3. go into rendered view
  4. unhide the cube -> causes the error

Event Timeline

Alaska (Alaska) changed the task status from Needs Triage to Confirmed.Sep 22 2021, 11:12 AM
Alaska (Alaska) changed the subtype of this task from "Report" to "Bug".
Alaska (Alaska) added a subscriber: Alaska (Alaska).

I can confirm. It should be noted that CUDA and OptiX show an error while rendering with the CPU results in Blender crashing.


System Information
Operating system: Linux-5.10.0-8-amd64-x86_64-with-glibc2.31 64 Bits
Graphics card: NVIDIA GeForce RTX 3090/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 470.74

Blender Version:
Broken version: 3.0.0 Alpha, branch: master, commit date: 2021-09-22 07:47, hash: rB90b485845caf

Alaska (Alaska) added a comment.EditedSep 22 2021, 11:16 AM

As a side note for @Henrik Dick (weasel) . If I remember correctly Cycles only officially supports GPU driver version 470 and above. You're running 460.73.01. Are you able to upgrade your drivers so you can avoid issues that might be caused by that in the future?