Subsurface scattering OpenCL Crash #57774

Closed
opened 4 years ago by Alaska · 8 comments
Alaska commented 4 years ago

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)
Alaska commented 4 years ago
Poster

Added subscriber: @Alaska

Added subscriber: @Alaska
Collaborator

Added subscribers: @brecht, @lichtwerk

Added subscribers: @brecht, @lichtwerk
brecht was assigned by lichtwerk 4 years ago
Collaborator

@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?
Alaska commented 4 years ago
Poster

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.
brecht commented 4 years ago
Owner

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.
Collaborator

This issue was referenced by blender/cycles@761d23db6c

This issue was referenced by blender/cycles@761d23db6c7ce8e14014864e5e9fba32838320a2
Collaborator

This issue was referenced by b7fb3296c1

This issue was referenced by b7fb3296c101bf408455352ec9784a8870672c81
brecht commented 4 years ago
Owner

Changed status from 'Open' to: 'Resolved'

Changed status from 'Open' to: 'Resolved'
brecht closed this issue 4 years ago
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/Collada
Interest/Compositing
Interest/Core
Interest/Cycles
Interest/Datablocks and Libraries
Interest/Dependency Graph
Interest/Development Management
Interest/Eevee
Interest/Eevee & Viewport
Interest/Freestyle
Interest/Geometry Nodes
Interest/Grease Pencil
Interest/Images & Movies
Interest/Import/Export
Interest/Line Art
Interest/Overrides
Interest/Performance
Interest/Pipeline, Assets & I/O
Interest/Translations
Interest/Undo
Interest/USD
Interest/Video Sequencer
legacy module/Animation & Rigging
legacy module/Core
legacy module/Development Management
legacy module/Eevee & Viewport
legacy module/Grease Pencil
legacy module/Modeling
legacy module/Nodes & Physics
legacy module/Pipeline, Assets & IO
legacy module/Platforms, Builds, Tests & Devices
legacy module/Python API
legacy module/Rendering & Cycles
legacy module/Sculpt, Paint & Texture
legacy module/Triaging
legacy module/User Interface
legacy module/VFX & Video
legacy project/1.0.0-beta.2
legacy project/Asset Browser (Archived)
legacy project/BF Blender: 2.8
legacy project/BF Blender: After Release
legacy project/BF Blender: Next
legacy project/BF Blender: Regressions
legacy project/BF Blender: Unconfirmed
legacy project/Blender 2.70
legacy project/Code Quest
legacy project/Game Animation
legacy project/Game Audio
legacy project/Game Data Conversion
legacy project/Game Engine
legacy project/Game Logic
legacy project/Game Physics
legacy project/Game Python
legacy project/Game Rendering
legacy project/Game UI
legacy project/GPU / Viewport
legacy project/GSoC
legacy project/Infrastructure: Websites
legacy project/LibOverrides - Usability and UX
legacy project/Masking
legacy project/Milestone 1: Basic, Local Asset Browser
legacy project/Modeling
legacy project/Modifiers
legacy project/Motion Tracking
legacy project/Nodes
legacy project/Nodes & Physics
legacy project/OpenGL Error
legacy project/Papercut
legacy project/Performance
legacy project/Physics
legacy project/Platforms, Builds, Tests & Devices
legacy project/Pose Library Basics
legacy project/Python API
legacy project/Render & Cycles
legacy project/Render Pipeline
legacy project/Retrospective
legacy project/Sculpt, Paint & Texture
legacy project/Text Editor
legacy project/Tracker Curfew
legacy project/Triaging
legacy project/User Interface
legacy project/UV Editing
legacy project/VFX & Video
legacy project/Virtual Reality
legacy project/Wintab High Frequency
Meta/Good First Issue
Meta/Papercut
migration/requires-manual-verification
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 & Devices
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 Information 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

No due date set.

Dependencies

No dependencies set.

Reference: blender/blender#57774
Loading…
There is no content yet.