Render crashes Blender when used with Volume Absorption #78027
Labels
No Label
Interest
Alembic
Interest
Animation & Rigging
Interest
Asset Browser
Interest
Asset Browser Project Overview
Interest
Audio
Interest
Automated Testing
Interest
Blender Asset Bundle
Interest
BlendFile
Interest
Collada
Interest
Compatibility
Interest
Compositing
Interest
Core
Interest
Cycles
Interest
Dependency Graph
Interest
Development Management
Interest
EEVEE
Interest
EEVEE & Viewport
Interest
Freestyle
Interest
Geometry Nodes
Interest
Grease Pencil
Interest
ID Management
Interest
Images & Movies
Interest
Import Export
Interest
Line Art
Interest
Masking
Interest
Metal
Interest
Modeling
Interest
Modifiers
Interest
Motion Tracking
Interest
Nodes & Physics
Interest
OpenGL
Interest
Overlay
Interest
Overrides
Interest
Performance
Interest
Physics
Interest
Pipeline, Assets & IO
Interest
Platforms, Builds & Tests
Interest
Python API
Interest
Render & Cycles
Interest
Render Pipeline
Interest
Sculpt, Paint & Texture
Interest
Text Editor
Interest
Translations
Interest
Triaging
Interest
Undo
Interest
USD
Interest
User Interface
Interest
UV Editing
Interest
VFX & Video
Interest
Video Sequencer
Interest
Virtual Reality
Interest
Vulkan
Interest
Wayland
Interest
Workbench
Interest: X11
Legacy
Blender 2.8 Project
Legacy
Milestone 1: Basic, Local Asset Browser
Legacy
OpenGL Error
Meta
Good First Issue
Meta
Papercut
Meta
Retrospective
Meta
Security
Module
Animation & Rigging
Module
Core
Module
Development Management
Module
EEVEE & Viewport
Module
Grease Pencil
Module
Modeling
Module
Nodes & Physics
Module
Pipeline, Assets & IO
Module
Platforms, Builds & Tests
Module
Python API
Module
Render & Cycles
Module
Sculpt, Paint & Texture
Module
Triaging
Module
User Interface
Module
VFX & Video
Platform
FreeBSD
Platform
Linux
Platform
macOS
Platform
Windows
Priority
High
Priority
Low
Priority
Normal
Priority
Unbreak Now!
Status
Archived
Status
Confirmed
Status
Duplicate
Status
Needs Info from Developers
Status
Needs Information from User
Status
Needs Triage
Status
Resolved
Type
Bug
Type
Design
Type
Known Issue
Type
Patch
Type
Report
Type
To Do
No Milestone
No project
No Assignees
20 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: blender/blender#78027
Loading…
Reference in New Issue
No description provided.
Delete Branch "%!s(<nil>)"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
System Information
Operating system: Windows 10
Graphics card: 5700 XT
Blender Version
Broken: 2.83
Worked: None, I am new to blender
Short description of error
Render crashes the whole application when used with OpenCL rendering with CPU+GPU or just GPU. The culprit is the Volume Absorption modifier. It does not crash when looking at the rendered mode within the viewport. Just the F12 final render. It works if I just use CPU rendering but that takes a lot longer.
Exact steps for others to reproduce the error
Donut.blend
#78870 was marked as duplicate of this issue
#78144 was marked as duplicate of this issue
Added subscriber: @turpentine
This is the exact moment the render hangs.
Added subscriber: @mano-wii
Changed status from 'Needs Triage' to: 'Needs User Info'
I cannot reproduce the problem.
Does the blender close or just hang?
Make sure that it is not the compilation of the kernels that is taking time.
You can see the compilation process in
Window -> Toogle System Console
Operating system: Windows-10-10.0.18941 64 Bits
Graphics card: Radeon (TM) RX 480 Graphics ATI Technologies Inc. 4.5.13596 Core Profile Context 20.10.19.02 27.20.1019.2002
It shows this for a bit, then spits out this
it hangs for about a minute and then closes.
Here is a guide on graphics problem in blender:
https://docs.blender.org/manual/en/dev/troubleshooting/gpu/index.html
Maybe some information there might help.
Btw, could you test other versions of blender (like 2.82)?
https://www.blender.org/download/previous-versions/
Thanks for following up. Tried going through that. My drivers are all up to date. It still crashes 2.82 with OpenCL enabled. If I go to None it renders but that is much slower. It's slower than even just using my processor on OpenCL only. Which is a combination that works.
Changed status from 'Needs User Info' to: 'Needs Triage'
Added subscriber: @mrguyorama
Hello, I just wanted to contribute my experience as I also ran into this issue. I am running an AMD 5700XT on Windows 10. I updated blender from 2.82 to 2.83 and my my driver to the 6/10/2020 driver from AMD and adding a volume absorption node to the default Principled BSDF shader and trying to render using GPU with OpenCL would cause blender to crash with no error message or useful info.
Downgrading to Blender version 2.82 and GPU driver 20.4.2 (released 5/15/2020) and running the same render, the shader compilation does not fail and blender does not crash and the render completes as expected.
Added subscriber: @Travis.SPN
Added subscriber: @SilentMrDave
Added subscriber: @Diogo_Valadares
I also just ran into this problem, my video card is an AMD 5700 XT on windows 10. I had no luck trying it in 2.9 neither in 2.83, and weirdly enough in 2.82 blender doesn't even want to render the default scene with a cube(it gets stuck compiling the kernels in the viewport and then crashes). GPU drivers are version 20.5.1 (5/25/2020).
2.9 gpu debug output rendering an object with principled volume:
blender_debug_output.txt
blender_system_info.txt
I just found out it will unfreze if you start rendering in the viewport and then you start to render before the viewport is done, after this it didn't get stuck anymore even if I close blender and reopen the same file.
Added subscriber: @xnonamex
Added subscriber: @zonaweb
Just to contribute.
I Have a RX570. I Made a Video that shows this issue here. Just add a volume node at default cube in a fresh file created. Cycles is Unusable for me with GPU.
Action 16-08-2020 21-15-40.mp4
Another thing I noted is that if I change to cyles on this newly created file (whithout volume node), my vram utilization is highly increased.
Action 16-08-2020 21-14-34.mp4
Added subscriber: @raphaelfalc
Hello,
I am having exactly the same issue with my RX 5700 XT.
So, I just want to add something here, when I'm working with volumetrics, after some time with blender open, If i'm with viewport render on and something is connected to the volumetrics output, If I disconnect it my blender just hangs really hard to the point that sometimes it crashes the whole windows too.
When it happens, it's usually a principled volume shader with some procedural textures on it. I tried to reproduce it only with a volume scatter, and after disconnecting, the blender recompiled the kerners for a second or two and then it freezed on this:
my gpu is an RX 5700 and I'm using the latest "stable" drivers (20.4.2)
Also I think the original bug from this thread isn't happening for me anymore in 2.90.1, tho I'd like to have some confirmation for this
I'm on an RX 5700XT with 20.9.2 on driver version and using Blender 2.90.1. I'm still getting crashes as in the original post but I'm also crashing even without using volumetrics. Cycles with CPU works fine but GPU still won't get past building the kernel.
@SilentMrDave this is already a Known problem(https://developer.blender.org/T75319) with the AMD beta drivers in the current generation and is not related to this thread. you can try it with the lastest stable drivers(20.4.2)
Added subscriber: @AndyMachin
Same problem. I am using latest driver 20.9.2 and blender 2.90.1 (this issue started to happen from 2.83). Viewport render freeze on 1st sample and I have to force stop blender.
Added subscriber: @aviel
I have the same issue in Linux. When using a volumetric shader, the GPU (5700 XT) usage goes up to 99% and blender freezes. Then even if I kill blender the GPU usage stays at 99% until I reboot the computer.
I am using blender 2.90.1 and using the latest AMDGPU-PRO version for Linux - 20.40
2020-10-10 17-30-44.mp4
Added subscriber: @HeyAshy
Hi Everyone,
I have new to blender but am having the exact same issue. The reder works fine until I add a volumetric shader and then just crashes on compiling the kernel.
I am running on a AMD Radeon RX5700 XT Red Devil, Intel i7-6700k with 32gb RAM.
Any help would be greatly appreciated.
@aviel Weirdly enough I already got that 99% once, you don't need to reboot your system, puting it in sleep mode and going back is enough and faster, tho for some reason I'm not getting stuck in the kernel compile part anymore, its rendering fine, tho I still have that problem of disconnecting the volume node while rendering.
my SO is windows and i'm using v20.4.2 drivers
I've continued testing a few things regarding the crash on my Linux machine.
I thought that maybe there's a problem with the opencl amdgpu-pro (pal) driver.
I tried to test its machine learning capabilities and I found out that I that some benchmarks get calculation errors, consistently (for example when I use the "plaidbench keras mobilenet" benchmark - using the plaidml tool). Then, when I switched to the rocm opencl driver, the errors were gone.
That suggests that the problem is in the opencl amdgpu pal driver.
Then I found that someone reported an issue that sounds exactly like that on a Windows machine:
https://community.amd.com/thread/248056
But they said that the issue should be fixed...
(If someone has a Windows machine, he can test the code from this forum page on his computer to check if the problem was actually fixed)
Added subscriber: @Alirion-2
This still is an Issue either thru Volume Absorption or even Mantaflow+principled BSDF - renders seem to stall after a certain density threshold has been reached. I noticed this again using 2.90.1 on Win 10 / RX 480 8GB using drivers 20.9.1. Also in Viewport Mode the Render does not pass the first Sample ( gets stuck there ).
Added subscriber: @ChloeHase
Definitely an RTX 5700 XT issue. I'm getting the same issue on Blender 2.83 when doing a GPU render with volumetric shaders. Seems to work absolutely fine on a CPU render with my Ryzen 5 3600. My current graphics driver is 20.5.1 but I'm updating to 20.9.2 as I speak. Will update with findings once I've updated.
Post-update, still no dice. Still crashes while 'updating device'. I'm going to try rolling back to 2.82 as suggested above.
Aaaaaand no joy with the rollback either. Same crash at the same stage. I'll try updating to 2.9.
No luck with that either.
@ChloeHase try to downgrade the driver to 20.4.2, its working "fine" on my 5700xt
Those quote marks don't give me hope! What's the downside?
@Diogo_Valadares Well I rolled back; it no longer crashes, but now my renders look like this.
@ChloeHase are you rendering with CPU+GPU?if so, this is a known issue https://developer.blender.org/T50193. I said "fine" with quotes because its a bit unstable thing and it tends to crash, like the example I made above
@Diogo_Valadares Ah, and here I was thinking ticking both of those under OpenCL would just make them both available, not use them both to render simultaneously. Weird, given I've never had that issue before with other renders! It works fine now.
Added subscriber: @Jasaj
I'm having the same problem. previewing and rendering perfectly fine with CPU. With the GPU, if the density isn't particularly high, items with Volume Absorption will show something completely wrong in preview mode, and sometimes render the right thing in render mode. If the density is very high, both preview and render mode will cause the system to crash. I even had problems with the blender benchmark using the GPU and couldn't run it to the end (CPU is fine).
If I hide the object in preview mode, the rest of the objects are displayed normally even with GPU, so I think it's a Volume Absorption issue.
I'm using a Radeon RX Vega 64.
Blender version 2.90.1
driver version 20.10.27.03-200826a-358464C-RadeonProEnterprise
Here are some of the tests I did. (I only made these changes: create a new file, add a volume, remove the surface)
shader
viewport shading CPU
viewport shading GPU
F12 GPU
(If using AMD ProRender)
Added subscriber: @Lafreyya
Same problem with Radeon R9 290 and blender 2.90
system-info.txt
Closed as duplicate of #77858
Added subscriber: @Shambles3D
If still someone has the problem. For me it worked when I installed the brand new version of Blender 2.91.0.
as I mentioned before, it is working for me since 2.90.1, but there is a caveat
F8940640
although I'm not sure if this problem persists with the last AMD driver update and blender 2.91, I might test it later
Removed subscriber: @SilentMrDave
Added subscriber: @Caesar17
Does anyone found a fix?
Added subscriber: @Daydreamingbackagain
I have Blender 2.93 and a Radeon Rx 560x and when I add volume absorption with Cycles GPU it just loads forever and says "Updating Device" and if I try to click anything it crashes, with CPU it loads inmediately.