Bug 2312407

Summary: Blender terminates (SIGSEGV) when using viewport shading for the GPU setting
Product: [Fedora] Fedora Reporter: alee14498
Component: blenderAssignee: Luya Tshimbalanga <luya_tfz>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 40CC: code, design-devel, epel-packagers-sig, kwizart, luya_tfz, negativo17
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
URL: https://www.youtube.com/watch?v=S0gBCNEiKIc
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2024-09-27 06:14:08 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
Crash Log none

Description alee14498 2024-09-15 03:08:58 UTC
When trying to change the device from CPU to GPU, and changing the viewport to rendered, it terminates my blender instance. But when trying to use the official Blender's binaries, it seems to be working as intended.

Reproducible: Always

Steps to Reproduce:
1. Open Blender
2. Open Render tab
3. Change Render Engine to Cycles
4. Change Device from CPU to GPU Compute
5. Click on "Viewport Shading"
Actual Results:  
Blender hangs for a bit, then terminates generating a crash log.

Expected Results:  
It should be showing the rendered scene.

CPU: AMD Ryzen 3 2200G
GPU: AMD Radeon RX 6600

Blender Version: 
Name         : blender
Epoch        : 1
Version      : 4.2.1
Release      : 3.fc40
Architecture : x86_64
Size         : 213 M
Source       : blender-4.2.1-3.fc40.src.rpm
Repository   : @System
From repo    : updates
Summary      : 3D modeling, animation, rendering and post-production
URL          : https://www.blender.org
License      : GPL-2.0-or-later
Description  : Blender is the essential software solution you need for 3D, from modeling,
             : animation, rendering and post-production to interactive creation and playback.
             : 
             : Professionals and novices can easily and inexpensively publish stand-alone,
             : secure, multi-platform content to the web, CD-ROMs, and other media.



Output
```
~ took 52s 
❯ blender --debug-gpu --debug-cycles
INFO (gpu.debug): Notification : Successfully hooked OpenGL debug callback using OpenGL 4.3
INFO (gpu.debug): Notification : Successfully hooked OpenGL debug callback using OpenGL 4.3

I0914 22:46:39.908576 117516 device.cpp:39] HIPEW initialization succeeded
I0914 22:46:39.908622 117516 device.cpp:41] Found precompiled kernels
I0914 22:46:39.935338 117516 device.cpp:212] Device has compute preemption or is not used for display.
I0914 22:46:39.935366 117516 device.cpp:216] Added device "AMD Radeon RX 6600" with id "HIP_AMD Radeon RX 6600_0000:03:00".
I0914 22:46:40.976343 117516 device.cpp:541] Mapped host memory limit set to 12,386,381,824 bytes. (11.54G)
I0914 22:46:40.976680 117516 device_impl.cpp:63] Using AVX2 CPU kernels.
Writing: /tmp/blender.crash.txt
fish: Job 1, 'blender --debug-gpu --debug-cyc…' terminated by signal SIGSEGV (Address boundary error)
```

Comment 1 alee14498 2024-09-15 03:11:23 UTC
Created attachment 2046912 [details]
Crash Log

Comment 2 Luya Tshimbalanga 2024-09-27 06:14:08 UTC
Know issue related to mixing LLVM version (18) used by Cycle Rendering with HIP (based on clang 17) hence segmentation fault on Cycle Rendering as finding out by both AMD and LLVM teams.
Let's move the problem on similar report.

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