https://projects.blender.org/blender/blender/issues/123841 looks like bug 2294166.

Yes. Do you know what could have caused the crashes?

The issue occurred when updating a dependency in this case OpenImageIO. Normally, a minor release from that dependency hardly impact the user interface but the exception happened.
Reading the https://projects.blender.org/blender/blender/issues/123841#issuecomment-1225965 report, a rebuild is needed. To simplify the process, let's move to bug #2294166.

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

Reopening as requested in !bug #2294166.

This issue is about the crashes reported in:

https://projects.blender.org/blender/blender/issues/123843

https://projects.blender.org/blender/blender/issues/123844

The crashes still happen after the update to blender-4.1.1-8.fc40.

Sorry – I help out from time to time with this package, but I’m not the right person to investigate this.

https://projects.blender.org/blender/blender/issues/123843 is a very reproducible crash, caused by packaging according to the Blender bug triaging team.

The issue is specifically related to ROCM HIP driver running AMD hardware. 
Using --debug-cycles parameters:
'''
I0717 21:27:19.060915 254744 device.cpp:39] HIPEW initialization succeeded
I0717 21:27:19.060968 254744 device.cpp:41] Found precompiled kernels
I0717 21:27:19.086841 254744 device.cpp:212] Device has compute preemption or is not used for display.
I0717 21:27:19.086892 254744 device.cpp:216] Added device "AMD Radeon Graphics" with id "HIP_AMD Radeon Graphics_0000:04:00".
I0717 21:27:22.075845 254849 device.cpp:541] Mapped host memory limit set to 27,076,481,024 bytes. (25.22G)
I0717 21:27:22.076308 254849 device_impl.cpp:63] Using AVX2 CPU kernels.
Writing: /tmp/RyzenGraphic_27.crash.txt
Segmentation fault (core dumped)
'''
Blender3D is build with HIP binary support. This bug reports is linked to rocclr from which the ticket is attacked as blocker.

Blender still crashes in the new 4.2 fedoraproject.org build, but the build from blender.org/download/ does not crash.

Would you provide which AMD hardware your system is running? In my case, the failure occurs on HIP 6.1.2 with AMD Ryzen 7 5825U (GCN 5.1) while the upstream version uses HIP 5.7. See https://rocm.docs.amd.com/projects/install-on-linux/en/latest/reference/system-requirements.html

It's a Ryzen 9 7900X CPU and a 7900XTX GPU. I have rocm-hip 6.1.2-1.fc40 installed.

I was able to reproduce the issue with a Ryzen 9 5900X CPU and Radeon 6950XT GPU on both upstream Blender and this package. Upstream uses pre-built HIP from possibly 5.7 (https://projects.blender.org/blender/blender/src/commit/ed8872218756ce38e7e8d9981c1a27c8dd6014ef/build_files/build_environment/cmake/versions.cmake). It will be best to work with rocclr maintainers as I am unable to fully debug the bug.

(In reply to fygdxcyw from comment #7)
> https://projects.blender.org/blender/blender/issues/123843 is a very
> reproducible crash, caused by packaging according to the Blender bug
> triaging team.

Upstream reopened the issue as the bug affected them as highlighted on 
https://devtalk.blender.org/t/cycles-amd-hip-device-feedback/21400/609

*** Bug 2296218 has been marked as a duplicate of this bug. ***

There is new insight on this issue in the thread on blender.org

https://projects.blender.org/blender/blender/issues/123843

They are closing the issue on blender.org because of inactivity.

I have tried a couple of samples 
https://www.blender.org/download/demo-files/#cycles
on rawhide and rocm 6.2, without an issue

Is this issue reproducible on on rawhide ?
What is the input file ?

The gpu i am using is
> rocminfo
...
  Name:                    gfx1100                            
  Uuid:                    GPU-2df31bb3e575db4c               
  Marketing Name:          AMD Radeon RX 7900 XTX

@Tom.Rix
I am using the same GPU. It happens every time the GPU is used with Cycles (viewport or final render). Are you sure that you are rendering using the GPU, not CPU? Are you using the Fedora package of Blender?

These are the exact steps to reproduce this crash, as listed in the bug report on blender.org, and what they mean:

Be on an up to date Fedora 40 machine
Have Blender installed from the Fedora Repository
Open Blender
Have the GPU active under HIP in the Blender Preferences (preferences -> system -> HIP -> AMD Radeon RX 7900 XTX)
Switch the viewport to Cycles (In the properties editor on the right side click on the camera icon "render properties" and switch the render engine from EEVEE to Cycles)
Under Render Properties switch Device to GPU Compute (Just below where you just switched to Cycles, switch the Device from CPU to GPU)
Blender Crashes (when you press F12 or switch the viewport to Cycles using the orbs in the top right)

FEDORA-2024-537c372a44 (rocm-compilersupport-17.3-5.rocm6.1.2.fc40) has been submitted as an update to Fedora 40.
https://bodhi.fedoraproject.org/updates/FEDORA-2024-537c372a44

Also needs this.
https://src.fedoraproject.org/rpms/clang17/pull-request/4
To get static clang libs to build against.

verified on M780/gfx1103.

This will be needed in F41 before clang18 hits
https://src.fedoraproject.org/rpms/clang18/pull-request/1

FEDORA-2024-537c372a44 has been pushed to the Fedora 40 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2024-537c372a44`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2024-537c372a44

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

*** Bug 2312407 has been marked as a duplicate of this bug. ***

FEDORA-2024-1b43e5339b has been pushed to the Fedora 40 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2024-1b43e5339b`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2024-1b43e5339b

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

I was able to reproduce this on f40:

curl -O -L https://mirrors.iu13.net/blender/demo/bundles/bundles-3.0/asset-demo-bundle-3.0-cube-diorama.zip
unzip asset-demo-bundle-3.0-cube-diorama.zip
cd cube_diorama
blender  -b --debug-cycles -E CYCLES -f 20 cube_diorama.blend -- --cycles-device HIP --cycles-print-stats


This crashes with the bactrace:

# backtrace
blender(+0xf6f05a) [0x5618d9aa805a]
blender(+0x927b9b) [0x5618d9460b9b]
/lib64/libc.so.6(+0x40d00) [0x7f9efcc4fd00]
/usr/lib64/llvm17/lib/libLLVM-17.so(_ZNK4llvm3opt8OptTable11ParseOneArgERKNS0_7ArgListERjjj+0x2c0) [0x7f9e91a12a30]
/usr/lib64/llvm17/lib/libLLVM-17.so(_ZNK4llvm3opt8OptTable9ParseArgsENS_8ArrayRefIPKcEERjS6_jj+0x1d5) [0x7f9e91a12e25]
/lib64/libamd_comgr.so.2(+0x1adcc) [0x7f9e9b21adcc]
/lib64/libamd_comgr.so.2(+0x1dcbe) [0x7f9e9b21dcbe]
/lib64/libamd_comgr.so.2(amd_comgr_do_action+0x1eb6) [0x7f9e9b22bdc6]
/lib64/libamdhip64.so(+0x2e2907) [0x7f9e9bee2907]
/lib64/libamdhip64.so(+0x2ee856) [0x7f9e9beee856]
/lib64/libamdhip64.so(+0x35338c) [0x7f9e9bf5338c]
/lib64/libamdhip64.so(+0x33f73d) [0x7f9e9bf3f73d]
/lib64/libamdhip64.so(+0x30f3ad) [0x7f9e9bf0f3ad]
/lib64/libamdhip64.so(+0x34f840) [0x7f9e9bf4f840]
/lib64/libamdhip64.so(+0x34fa66) [0x7f9e9bf4fa66]
/lib64/libamdhip64.so(+0x2620f4) [0x7f9e9be620f4]
/lib64/libamdhip64.so(+0x262b50) [0x7f9e9be62b50]
blender(+0x2803fd0) [0x5618db33cfd0]
blender(+0x28040bf) [0x5618db33d0bf]
blender(+0x2c932cb) [0x5618db7cc2cb]
blender(+0x2c9383c) [0x5618db7cc83c]
blender(+0x277fd17) [0x5618db2b8d17]
blender(+0x2767069) [0x5618db2a0069]
blender(+0x2769038) [0x5618db2a2038]
/lib64/libpython3.12.so.1.0(+0x190428) [0x7f9efdb90428]
/lib64/libpython3.12.so.1.0(_PyObject_MakeTpCall+0x76) [0x7f9efdb69016]
/lib64/libpython3.12.so.1.0(_PyEval_EvalFrameDefault+0xb37) [0x7f9efdb71a87]
blender(+0x15e4c65) [0x5618da11dc65]
blender(+0x1527401) [0x5618da060401]
blender(+0x33d178d) [0x5618dbf0a78d]
blender(+0x1d9778e) [0x5618da8d078e]
blender(+0x1d97d34) [0x5618da8d0d34]
blender(+0x1d97fd8) [0x5618da8d0fd8]
blender(+0x1d9906d) [0x5618da8d206d]
blender(+0x1d9a48f) [0x5618da8d348f]
blender(+0x9484c4) [0x5618d94814c4]
blender(+0xf8bedd) [0x5618d9ac4edd]
blender(+0x8d099f) [0x5618d940999f]
/lib64/libc.so.6(+0x2a088) [0x7f9efcc39088]
/lib64/libc.so.6(__libc_start_main+0x8b) [0x7f9efcc3914b]
blender(+0x91bf15) [0x5618d9454f15]

# Python backtrace

FEDORA-2024-1b43e5339b (rocm-compilersupport-17.3-6.rocm6.1.2.fc40) has been pushed to the Fedora 40 stable repository.
If problem still persists, please make note of it in this bug report.

Reopening for clang related issue.

FEDORA-2024-3f027d3cb6 (clang17-17.0.6-9.fc40 and rocm-compilersupport-17.3-7.rocm6.1.2.fc40) has been submitted as an update to Fedora 40.
https://bodhi.fedoraproject.org/updates/FEDORA-2024-3f027d3cb6

FEDORA-2024-3f027d3cb6 has been pushed to the Fedora 40 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2024-3f027d3cb6`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2024-3f027d3cb6

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

FEDORA-2024-3f027d3cb6 (clang17-17.0.6-9.fc40 and rocm-compilersupport-17.3-7.rocm6.1.2.fc40) has been pushed to the Fedora 40 stable repository.
If problem still persists, please make note of it in this bug report.

Still crashes.  Fedora 40 up to date as of 10/23/24.

Ryzen 5 5600X
AMD RX 6650XT

Rendering anything more complex than a donut, like trying to render the benchmark files on the dGPU crashes Blender.

# Blender 4.2.1, Commit date: 1970-01-01 00:00, Hash unknown

# backtrace
blender(+0xf6f05a) [0x5568c9b1b05a]
blender(+0x927b9b) [0x5568c94d3b9b]
/lib64/libc.so.6(+0x40d00) [0x7f93ade4fd00]
/usr/lib64/llvm17/lib/libLLVM-17.so(_ZNK4llvm3opt8OptTable11ParseOneArgERKNS0_7ArgListERjjj+0x2c0) [0x7f930a012a30]
/usr/lib64/llvm17/lib/libLLVM-17.so(_ZNK4llvm3opt8OptTable9ParseArgsENS_8ArrayRefIPKcEERjS6_jj+0x1d5) [0x7f930a012e25]
/lib64/libamd_comgr.so.2(+0x1adcc) [0x7f9312e1adcc]
/lib64/libamd_comgr.so.2(+0x1dcba) [0x7f9312e1dcba]
/lib64/libamd_comgr.so.2(amd_comgr_do_action+0x1eb6) [0x7f9312e2bdc6]
/lib64/libamdhip64.so(+0x2e2ec0) [0x7f9313ae2ec0]
/lib64/libamdhip64.so(+0x2eedc6) [0x7f9313aeedc6]
/lib64/libamdhip64.so(+0x353a2c) [0x7f9313b53a2c]
/lib64/libamdhip64.so(+0x33fdea) [0x7f9313b3fdea]
/lib64/libamdhip64.so(+0x30f8cd) [0x7f9313b0f8cd]
/lib64/libamdhip64.so(+0x34fec0) [0x7f9313b4fec0]
/lib64/libamdhip64.so(+0x3500e6) [0x7f9313b500e6]
/lib64/libamdhip64.so(+0x262474) [0x7f9313a62474]
/lib64/libamdhip64.so(+0x262ed0) [0x7f9313a62ed0]
blender(+0x2803fd0) [0x5568cb3affd0]
blender(+0x28040bf) [0x5568cb3b00bf]
blender(+0x2c932cb) [0x5568cb83f2cb]
blender(+0x2c9383c) [0x5568cb83f83c]
blender(+0x277fd17) [0x5568cb32bd17]
blender(+0x2767069) [0x5568cb313069]
blender(+0x2769038) [0x5568cb315038]
/lib64/libpython3.12.so.1.0(+0x190428) [0x7f93aed90428]
/lib64/libpython3.12.so.1.0(_PyObject_MakeTpCall+0x76) [0x7f93aed69016]
/lib64/libpython3.12.so.1.0(_PyEval_EvalFrameDefault+0xb37) [0x7f93aed71a87]
blender(+0x15e4c65) [0x5568ca190c65]
blender(+0x1527401) [0x5568ca0d3401]
blender(+0x33d178d) [0x5568cbf7d78d]
blender(+0x1d9778e) [0x5568ca94378e]
blender(+0x1d97d34) [0x5568ca943d34]
blender(+0x1d97fd8) [0x5568ca943fd8]
blender(+0x1d9906d) [0x5568ca94506d]
blender(+0x1d99cd6) [0x5568ca945cd6]
blender(+0x1b8a07d) [0x5568ca73607d]
blender(+0xfbd331) [0x5568c9b69331]
/lib64/libc.so.6(+0x976d7) [0x7f93adea66d7]
/lib64/libc.so.6(+0x11b60c) [0x7f93adf2a60c]

# Python backtrace

(on comment #31)

I realize the Fedora maintainers may not be able to do anything about my crash since it's on an RX 6650XT.  This is probably something only AMD can fix as they refuse to support any dGPU other than RX 79xx on Linux for HIP.  But I figured I'd report the bug and see what, if anything, can be done.

Reopening as the missing parts needed to fix HIP support for Cycle Rendering running clang affecting both Fedora 41, (possibly F40) and Rawhide: 
- https://src.fedoraproject.org/rpms/clang18/pull-request/1
- https://src.fedoraproject.org/rpms/clang18/pull-request/2

(In reply to Tom.Rix from comment #20)
> Also needs this.
> https://src.fedoraproject.org/rpms/clang17/pull-request/4
> To get static clang libs to build against.
> 
> verified on M780/gfx1103.

Problem still exists.
Verified on another gpu M680/gfx1051, that statically linking libcomgr will fix the problem.

@Tom: Just to clarify, you're saying that the problem still exists on f40 built against clang17 with the clang symbol versioning change? (Rather than f41 built against clang18, which doesn't have the patch yet.)

I verified the problem still exists on F40, that has I believe the symbol version change.
Then I rebuilt clang17 with the PR/4, which reenables the clang static libs.
Then I rebuilt comgr with that clang17's static libs and installed.
Then blender behaved as expected.

We still need to merge https://src.fedoraproject.org/rpms/clang/pull-request/249# and then rebuild blender.  I'll get started on that.

@luya Is it OK if I rebuild blender in this side-tag: f40-build-side-99646

@tstellar Go for it along other branches i.e both f41 and Rawhide.

FEDORA-2024-0b42137285 (blender-4.2.3-2.fc40 and clang-18.1.8-2.fc40) has been submitted as an update to Fedora 40.
https://bodhi.fedoraproject.org/updates/FEDORA-2024-0b42137285

FEDORA-2024-0b42137285 has been pushed to the Fedora 40 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2024-0b42137285`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2024-0b42137285

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

It is still broken on Fedora 41.

Did the patch not land in Fedora 41, or does the patch not resolve the issue?

It's been 8 months since opening this report.
Any updates on this urgent severity bug, that still crashes the application?

I believe this works in F42, but it depends on changing the compiler to rocm-llvm.
I have not checked F40 or F41.

I was originally added to the maintainers list for the blender package so that I could rebuild it for usd updates (before I became a provenpackager). I do occasionally help out with build issues and such when I can, but I don’t take responsibility for the package as a primary maintainer. I’m therefore clearing my NEEDINFO.

The Blender bug triaging team is asking for updates on this issue.
https://projects.blender.org/blender/blender/issues/123843

Note from Blender developer Sergey Sharybin: 
> P.S. Also keep in mind that Blender 4.4 contains quite some fixes for HIP and HIP-RT, including fixes needed to ensure proper SDK version is loaded etc.

Blender loads at runtime libllvm,clang.so's because it uses libraries that have these libraries.  
Then when cycles is used, blender dlopen's libamd_comgr.so, which in F40 and F41 also has libllvm,clang,lld.so's dependencies.
The former dependencies use one version of llvm, the later an older version.  This is a known problem with llvm.

The fix mentioned here, is to turn on symbol versioning.
I do not know if that works.

In F42+ libamd_comgr.so is linked with libllvm,clang,lld.a, not *.so, so there is no llvm runtime to conflict with.
This is done as part of the rocm-llvm toolchain build, rocm-llvm is new for F42.

Doing this fix in F40,F41 is not possible because the system and compat llvm,clang,lld's do not have all the necessary *.a's

For blender 4.4
Fedora will have the latest ROCm available.
There is a HIP-RT, 2.5.cfa5e2a, is this sufficient for 4.4 or do we need to update to the just released version 2.5.9904ddc?

Can you test Blender 4.2.8 which is the latest LTS release? Thanks.

(In reply to Tom.Rix from comment #48)
> 
> For blender 4.4
> Fedora will have the latest ROCm available.
> There is a HIP-RT, 2.5.cfa5e2a, is this sufficient for 4.4 or do we need to
> update to the just released version 2.5.9904ddc?

Blender 4.4 runs better with HIP-RT 2.5.9904ddc which include missing libraries on Fedora 42 as tested on Radeon RX 6950 XT. It will be ideal to carry over HIP-RT 2.5.9904ddc as a bug fix for Fedora 42 aside Rawhide now that Blender 4.4 is available for all but Fedora 40 which reach EOL next month assuming the reporter updated to the latest release.

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.

Lets close this report as Fedora 40 reaches EOL assuming the reporter moved to the latest stable release.