Blender just crashes for no reason, and the crash report is empty. (Segmentation fault) #111834

New Issue

Jackson-Novak-1 · 2023-09-02T20:11:41+02:00

Jackson-Novak-1 commented

2023-09-02 20:11:41 +02:00

System Information
Operating system: Arch Linux x86_64
Graphics card: AMD Radeon RX 6900 XT

Blender Version
Broken: (example: 3.6.2, ffe9313875, master, 2023-08-31, as found on the splash screen)
Worked: (No idea when this error started happening.)

Short description of error
Blender does not start up. When I start it via the command line, I get this error:

Writing: /tmp/blender.crash.txt
Segmentation fault (core dumped)

/tmp/blender.crash.txt:

# Blender 3.6.2, Commit date: 2023-08-14 14:05, Hash ffe93138751e

# backtrace

# Python backtrace

Exact steps for others to reproduce the error
Trying to open Blender.

**System Information** Operating system: Arch Linux x86_64 Graphics card: AMD Radeon RX 6900 XT **Blender Version** Broken: (example: 3.6.2, ffe93138751e, master, 2023-08-31, as found on the splash screen) Worked: (No idea when this error started happening.) **Short description of error** Blender does not start up. When I start it via the command line, I get this error: ``` Writing: /tmp/blender.crash.txt Segmentation fault (core dumped) ``` `/tmp/blender.crash.txt`: ``` # Blender 3.6.2, Commit date: 2023-08-14 14:05, Hash ffe93138751e # backtrace # Python backtrace ``` **Exact steps for others to reproduce the error** Trying to open Blender.

image.png

28 KiB

👍 2

Jackson-Novak-1 added the

labels 2023-09-02 20:11:42 +02:00

Ailac commented

2023-09-03 07:28:06 +02:00

Same here, the log is just in blank with no stack trace like the OP

System Information
Operating system: Endeavour OS x86_64
Graphics card: AMD Radeon RX 6700 XT
CPU: Intel Core i7-4790

Same here, the log is just in blank with no stack trace like the OP System Information Operating system: Endeavour OS x86_64 Graphics card: AMD Radeon RX 6700 XT CPU: Intel Core i7-4790

Ayodele Arigbabu commented

2023-09-03 17:10:19 +02:00

Experienced this too, running Manjaro Linux, 32GB ram and Nvidia RTX 3060ti with 8GB Vram

Iliya Katushenock commented

2023-09-03 17:25:02 +02:00

Can you check blender 4.0?

Ayodele Arigbabu commented

2023-09-03 19:54:58 +02:00

Same experience with Blender 4.0

Frank-Carlyle-McLaughlin commented

2023-09-04 01:21:41 +02:00

The Arch maintainers are aware of this: https://bugs.archlinux.org/task/79506 -- you can add votes to that bug.

It seems to have something to do with OpenShadingLanguage not supporting LLVM 16, although for all I know it's potentially related to blender/blender#111820.

The Arch maintainers are aware of this: https://bugs.archlinux.org/task/79506 -- you can add votes to that bug. It seems to have something to do with OpenShadingLanguage not supporting LLVM 16, although for all I know it's potentially related to blender/blender#111820.

👍 1

YimingWu commented

2023-09-04 05:33:46 +02:00

It seems to have something to do with OpenShadingLanguage not supporting LLVM 16

I guess it is possible, maybe the binaries are compiled differently. Are you using your own compilation of blender?

> It seems to have something to do with OpenShadingLanguage not supporting LLVM 16 I guess it is possible, maybe the binaries are compiled differently. Are you using your own compilation of blender?

Frank-Carlyle-McLaughlin commented

2023-09-04 06:30:14 +02:00

It seems to have something to do with OpenShadingLanguage not supporting LLVM 16

I guess it is possible, maybe the binaries are compiled differently. Are you using your own compilation of blender?

I've tried (1) Arch's precompiled package, and (2) my own compilation.

(1) Arch's Blender package will launch if I use the trick of specifying drivers and libraries from the LLVM 15 version of Mesa (as noted in the Arch bug discussion), although Cycles will sometimes (but not always) crash. Arch appears to compile Blender and OpenShadingLanguage and other components with LLVM 15, but Mesa with LLVM 16. If you look through the Arch bug discussion, there are some stacktraces there, and one of the comments notes that the "Common factor seems to be radeonsi driver and aforementioned LLVM conflict."

(2) My own compilation is not a "controlled experiment" due to #111820, but it does launch fine if I compile it using LLVM 16 and without OpenShadingLanguage support. On the whole, I question whether this is really a Blender bug rather than an issue with OpenShadingLanguage not yet supporting LLVM 16 and/or Arch deciding to move to LLVM 16.

> > It seems to have something to do with OpenShadingLanguage not supporting LLVM 16 > > I guess it is possible, maybe the binaries are compiled differently. Are you using your own compilation of blender? I've tried (1) Arch's precompiled package, and (2) my own compilation. (1) Arch's Blender package will launch if I use the trick of specifying drivers and libraries from the LLVM 15 version of Mesa (as noted in the Arch bug discussion), although Cycles will sometimes (but not always) crash. Arch appears to compile Blender and OpenShadingLanguage and other components with LLVM 15, but Mesa with LLVM 16. If you look through the Arch bug discussion, there are some stacktraces there, and one of the comments notes that the "Common factor seems to be radeonsi driver and aforementioned LLVM conflict." (2) My own compilation is not a "controlled experiment" due to #111820, but it does launch fine _if_ I compile it using LLVM 16 and without OpenShadingLanguage support. On the whole, I question whether this is really a Blender bug rather than an issue with OpenShadingLanguage not yet supporting LLVM 16 and/or Arch deciding to move to LLVM 16.

YimingWu added

Module

Platforms, Builds & Tests

Status

Needs Info from Developers

and removed

Status

Needs Triage

labels 2023-09-04 07:20:08 +02:00

Frank-Carlyle-McLaughlin referenced this issue

2023-09-04 19:29:44 +02:00

Compilation of GHOST_XrGraphicsBinding.cc fails with "invalid conversion" error #111820