Bug 2296218 - Blender crashes when rendering with GPU Compute on Cycles
Summary: Blender crashes when rendering with GPU Compute on Cycles
Keywords:
Status: CLOSED DUPLICATE of bug 2294591
Alias: None
Product: Fedora
Classification: Fedora
Component: blender
Version: 40
Hardware: x86_64
OS: Linux
unspecified
unspecified
Target Milestone: ---
Assignee: Luya Tshimbalanga
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2024-07-07 23:08 UTC by flavonol
Modified: 2024-08-25 06:32 UTC (History)
6 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2024-08-25 06:32:18 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
A crash log from my attempt to render a new general project. (372 bytes, text/plain)
2024-07-07 23:08 UTC, flavonol
no flags Details

Description flavonol 2024-07-07 23:08:10 UTC
Created attachment 2039232 [details]
A crash log from my attempt to render a new general project.

Description of problem:
Rendering anything with the Cycles engine crashes Blender if Device is set to GPU Compute.

Version-Release number of selected component (if applicable):
4.1.1-8.fc40

How reproducible: 100% on my system

Steps to Reproduce:
1. Run blender from the command line.
2. Open a project or start a new general project.
3. Under Preferences > System > Cycles Render Devices > HIP, check the box labelled with the name of the graphics card.
4. In the Render panel, set Render Engine to Cycles.
5. Set Device to GPU Compute.
6. Set Viewport Shading to Rendered or hit the render hotkey.

Actual results:
Blender freezes for about 1 second, then crashes, leaving behind a crash log in /tmp/ (example attached).

Expected results:
An image of the scene should be rendered.

Additional info:

My graphics card is a Radeon RX 5700 XT.

Downloading Blender 4.1.1 directly from blender.org and running the executable from that tarball allows for GPU Compute rendering without crashing.

This problem did not occur until recently. Below is the history of the blender package on my system. As you can see, I reinstalled the package several times. I also tried reinstalling all packages with names starting with rocm, then rebooting.

ID     | Command line              | Date and time    | Action(s)      | Altered
--------------------------------------------------------------------------------
    64 | install blender           | 2024-07-07 17:47 | Install        |   22   
    63 | remove blender            | 2024-07-07 17:38 | Removed        |   22   
    62 | install blender           | 2024-07-07 17:35 | Install        |   22   
    61 | remove blender            | 2024-07-07 17:34 | Removed        |   22  <
    59 | install blender           | 2024-07-07 15:40 | Install        |   22 > 
    58 | remove blender            | 2024-07-07 15:39 | Removed        |   22  <
    41 | upgrade -y                | 2024-06-23 18:09 | C, E, I, O, U  |  339 ><
    15 |                           | 2024-05-27 17:11 | Install        |  121 >

Comment 1 Luya Tshimbalanga 2024-07-19 00:26:44 UTC
Hello, does the upstream version has HIP enabled when rendering with Cycle Rendering engine?

Comment 2 flavonol 2024-07-19 13:18:34 UTC
Yes, HIP on the RX 5700 XT is enabled for Cycles rendering on upstream version 4.1.1.

Comment 3 Luya Tshimbalanga 2024-08-25 06:30:25 UTC
It is an upstream issue as they built the Cycle Rendering Engine with rocm-hip 5.7 thus incompatible with HIP 6.x series.
https://devtalk.blender.org/t/cycles-amd-hip-device-feedback/21400/609

Comment 4 Luya Tshimbalanga 2024-08-25 06:32:18 UTC
Lets move the issue on a similar bug report.

*** This bug has been marked as a duplicate of bug 2294591 ***


Note You need to log in before you can comment on or make changes to this bug.