Bug 2298548 - Cycles Rendering silently traced back with ROCM HIP enabled support
Summary: Cycles Rendering silently traced back with ROCM HIP enabled support
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: rocclr
Version: 40
Hardware: x86_64
OS: Linux
unspecified
medium
Target Milestone: ---
Assignee: Jeremy Newton
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks: 2294591
TreeView+ depends on / blocked
 
Reported: 2024-07-18 04:14 UTC by Luya Tshimbalanga
Modified: 2025-05-20 19:14 UTC (History)
2 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2025-05-20 19:14:19 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Luya Tshimbalanga 2024-07-18 04:14:06 UTC
The crash of Cycle Renderer occurred with HIP support enabled for AMD graphic cards,

Reproducible: Always

Steps to Reproduce:
1. Open Blender application
2. Enable HIP support on Cycle Rendering Devices from Preferences
3. Render a 3D model with Cycle Rendering engine
Actual Results:  
Blender 3D will silently crash with no useful debugging information

Expected Results:  
Blender 3D should successfully render a 3D model with Cycle Rendering engine.

Comment 1 Luya Tshimbalanga 2024-08-17 07:25:53 UTC
Upstream Blender comes with bundled HIP 5.7 series which render Cycles engine fine. Testing on a Ryzen 9 5900X and Radeon RX 6950XT, tt seems the issues occurs with rocm-hip 6.1.2.

Comment 2 Luya Tshimbalanga 2024-08-19 15:45:09 UTC
More details on https://devtalk.blender.org/t/cycles-amd-hip-device-feedback/21400/609

Comment 3 Jeremy Newton 2024-09-27 22:52:01 UTC
Yeah we discovered the cause of the issue. We have two proposals available:
- statically compiling libclang17 and linking into rocm-comgr (upstream does this by default)
- the clang17 maintainers versioning the symbols to avoid conflicts with clang 18
Hopefully we can get this moving next week.

Comment 4 Luya Tshimbalanga 2024-09-28 17:43:35 UTC
Thank you for the update.

Comment 5 Aoife Moloney 2025-04-28 13:31:09 UTC
This message is a reminder that Fedora Linux 40 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora Linux 40 on 2025-05-13.
It is Fedora's policy to close all bug reports from releases that are no longer
maintained. At that time this bug will be closed as EOL if it remains open with a
'version' of '40'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, change the 'version' 
to a later Fedora Linux version. Note that the version field may be hidden.
Click the "Show advanced fields" button if you do not see it.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora Linux 40 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora Linux, you are encouraged to change the 'version' to a later version
prior to this bug being closed.

Comment 6 Aoife Moloney 2025-05-20 19:14:19 UTC
Fedora Linux 40 entered end-of-life (EOL) status on 2025-05-13.

Fedora Linux 40 is no longer maintained, which means that it
will not receive any further security or bug fix updates. As a result we
are closing this bug.

If you can reproduce this bug against a currently maintained version of Fedora Linux
please feel free to reopen this bug against that version. Note that the version
field may be hidden. Click the "Show advanced fields" button if you do not see
the version field.

If you are unable to reopen this bug, please file a new report against an
active release.

Thank you for reporting this bug and we are sorry it could not be fixed.


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