Subsurface scattering OpenCL Crash #57774

Closed
opened 2018-11-11 06:19:35 +01:00 by Alaska · 8 comments
Member

System Information:
CPU: Ryzen 5 2600
GPU: RX 570 4gb (Radeon Software Version: 18.11.1)
OS: Windows 10 home

Blender Version:
Broken: blender-2.80-2c2c996a1b2 (November 9th)
Worked: Blender 2.79b and Blender 2.79 Master

Short description of error:
Whenever I use a Principaled BSDF with Subsurface Scatting enabled in Cycles and the pixel count is high enough (Changing the viewport pixel size to 8x or 4x on my 1440x900 monitor resolves this issue), Blender will freeze and the screen will flash black (probably from a GPU driver crash) then Blender will remain white and "Not Responding". I would write this off as a driver issue, but seeing as these issues don't occur in Blender 2.79b or 2.79 master, it seems to be an issue with Blender 2.8 not the driver (I may be wrong on this assumption).

The error I receive from Blender after the screen flickering with the --debug-cycles argument is:

AL lib: (EE) ALCmmdevPlayback_mixerProc: Failed to get padding: 0x88890004

If I understand correctly, this is something to do with Audio and may simply be Blender interfacing with the GPU after it crashes, but I'll leave it in here just in cause I'm wrong on this assumption.

Note: Final renders don't appear to be affected by this crash. However, if the scene is official rendered (F12) then we switch back to viewport, the freezing and crashing are no longer there. However, artifacts appear:
Artifacts.PNG

Exact steps for others to reproduce the error:
Here's a file to test with:
Subsurface Scattering Crash.blend

**System Information:** CPU: Ryzen 5 2600 GPU: RX 570 4gb (Radeon Software Version: 18.11.1) OS: Windows 10 home **Blender Version:** Broken: blender-2.80-2c2c996a1b2 (November 9th) Worked: Blender 2.79b and Blender 2.79 Master **Short description of error:** Whenever I use a Principaled BSDF with Subsurface Scatting enabled in Cycles and the pixel count is high enough (*Changing the viewport pixel size to 8x or 4x on my 1440x900 monitor resolves this issue*), Blender will freeze and the screen will flash black (*probably from a GPU driver crash*) then Blender will remain white and "Not Responding". I would write this off as a driver issue, but seeing as these issues don't occur in Blender 2.79b or 2.79 master, it seems to be an issue with Blender 2.8 not the driver (*I may be wrong on this assumption*). The error I receive from Blender after the screen flickering with the --debug-cycles argument is: ``` AL lib: (EE) ALCmmdevPlayback_mixerProc: Failed to get padding: 0x88890004 ``` If I understand correctly, this is something to do with Audio and may simply be Blender interfacing with the GPU after it crashes, but I'll leave it in here just in cause I'm wrong on this assumption. Note: Final renders don't appear to be affected by this crash. However, if the scene is official rendered (F12) then we switch back to viewport, the freezing and crashing are no longer there. However, artifacts appear: ![Artifacts.PNG](https://archive.blender.org/developer/F5490044/Artifacts.PNG) **Exact steps for others to reproduce the error:** Here's a file to test with: [Subsurface Scattering Crash.blend](https://archive.blender.org/developer/F5488400/Subsurface_Scattering_Crash.blend)
Author
Member

Added subscriber: @Alaska

Added subscriber: @Alaska
Member

Added subscribers: @brecht, @lichtwerk

Added subscribers: @brecht, @lichtwerk
Brecht Van Lommel was assigned by Philipp Oeser 2018-11-12 13:02:33 +01:00
Member

@brecht: not sure if you have access to such hardware, mind having a look?

@brecht: not sure if you have access to such hardware, mind having a look?
Author
Member

I conducted another test on my Ryzen 5 2500u with Vega 8 graphics and found it experienced a similar issue. However, in the case of this GPU, a "Blue screen of death" occured with the message VIDEO_TDR_FAILURE. However, in the case of this GPU, the same issue occurs for Blender 2.79 master.

I believe the issue experienced on this system is probably more related to the low-endness of the system than the Sub-surface scattering. But it brought up the question, is the issue experienced with the RX 570 just the GPU timing out due to the complexity of the Sub-surface scattering material? With this in mind I conducted another test: A 2.79 Master scene with an indoor scene with a glass sphere, mirror, and multiple objects with sub-surface scattering. And surprisingly the GPU didn't crash.

I still believe it's an issue with 2.8 and probably Open CL.

I conducted another test on my Ryzen 5 2500u with Vega 8 graphics and found it experienced a similar issue. However, in the case of this GPU, a "Blue screen of death" occured with the message VIDEO_TDR_FAILURE. However, in the case of this GPU, the same issue occurs for Blender 2.79 master. I believe the issue experienced on this system is probably more related to the low-endness of the system than the Sub-surface scattering. But it brought up the question, is the issue experienced with the RX 570 just the GPU timing out due to the complexity of the Sub-surface scattering material? With this in mind I conducted another test: A 2.79 Master scene with an indoor scene with a glass sphere, mirror, and multiple objects with sub-surface scattering. And surprisingly the GPU didn't crash. I still believe it's an issue with 2.8 and probably Open CL.

Can you try testing with the latest builds?

I was never able to reproduce this problem (even on a 4K monitor), but there have been some fixes in this area.

Can you try testing with the latest builds? I was never able to reproduce this problem (even on a 4K monitor), but there have been some fixes in this area.

This issue was referenced by blender/cycles@761d23db6c

This issue was referenced by blender/cycles@761d23db6c7ce8e14014864e5e9fba32838320a2

This issue was referenced by b7fb3296c1

This issue was referenced by b7fb3296c101bf408455352ec9784a8870672c81

Changed status from 'Open' to: 'Resolved'

Changed status from 'Open' to: 'Resolved'
Sign in to join this conversation.
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
4 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: blender/blender#57774
No description provided.