I'm not sure Vulkan is the issue here. I would try run the created core in gdb and make a backtrace. And also try again with packages

libvulkan_intel
libvulkan_intel-32bit

uninstalled.

(In reply to Stefan Dirsch from comment #1)
> I'm not sure Vulkan is the issue here. I would try run the created core in
> gdb and make a backtrace. And also try again with packages
> 
> libvulkan_intel
> libvulkan_intel-32bit
> 
> uninstalled.

libvulkan_intel* are uninstalled, but the result are same as previous.

Please refer to attached coredump info.

Created attachment 874139 [details]
Gerneated by command "coredumpctl info 5103"

Created attachment 874140 [details]
chrome core dump file

(In reply to Dawei Pang from comment #2)
> (In reply to Stefan Dirsch from comment #1)
> > I'm not sure Vulkan is the issue here. I would try run the created core in
> > gdb and make a backtrace. And also try again with packages
> > 
> > libvulkan_intel
> > libvulkan_intel-32bit
> > 
> > uninstalled.
> 
> libvulkan_intel* are uninstalled, but the result are same as previous.

Really? Still these messages

MESA-INTEL: warning: Haswell Vulkan support is incomplete

This sounds weird then.

> Please refer to attached coredump info.

There's nothing in there, which points to Mesa as the culprit.

(In reply to Stefan Dirsch from comment #5)
> (In reply to Dawei Pang from comment #2)
> > (In reply to Stefan Dirsch from comment #1)
> > > I'm not sure Vulkan is the issue here. I would try run the created core in
> > > gdb and make a backtrace. And also try again with packages
> > > 
> > > libvulkan_intel
> > > libvulkan_intel-32bit
> > > 
> > > uninstalled.
> > 
> > libvulkan_intel* are uninstalled, but the result are same as previous.
> 
> Really? Still these messages
> 
> MESA-INTEL: warning: Haswell Vulkan support is incomplete
> 
> This sounds weird then.
> 
> > Please refer to attached coredump info.
> 
> There's nothing in there, which points to Mesa as the culprit.

It is true since comment#2

pangdae@localhost:~> rpm -qa | grep vulkan
libvulkan1-1.3.280.0-1.2.x86_64
Mesa-vulkan-device-select-24.0.3-372.1.x86_64
vulkan-tools-1.3.280.0-1.2.x86_64

pangdae@localhost:~> /opt/google/chrome/chrome
[0409/165745.348709:WARNING:chrome_main_linux.cc(80)] Read channel stable from /opt/google/chrome/CHROME_VERSION_EXTRA
[3166:3166:0409/165745.891082:ERROR:gpu_process_host.cc(1002)] GPU process exited unexpectedly: exit_code=139
[3166:3166:0409/165746.282455:ERROR:gpu_process_host.cc(1002)] GPU process exited unexpectedly: exit_code=139
[3166:3186:0409/165746.469308:ERROR:object_proxy.cc(576)] Failed to call method: org.freedesktop.DBus.StartServiceByName: object_path= /org/freedesktop/DBus: org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
[3166:3166:0409/165746.703090:ERROR:gpu_process_host.cc(1002)] GPU process exited unexpectedly: exit_code=139
[3166:3166:0409/165747.113671:ERROR:gpu_process_host.cc(1002)] GPU process exited unexpectedly: exit_code=139
[3166:3166:0409/165747.515077:ERROR:gpu_process_host.cc(1002)] GPU process exited unexpectedly: exit_code=139
[3166:3166:0409/165747.928665:ERROR:gpu_process_host.cc(1002)] GPU process exited unexpectedly: exit_code=139
[3166:3166:0409/165748.253043:ERROR:gpu_process_host.cc(1002)] GPU process exited unexpectedly: exit_code=139
[3166:3166:0409/165748.572359:ERROR:gpu_process_host.cc(1002)] GPU process exited unexpectedly: exit_code=139
INFO: Created TensorFlow Lite XNNPACK delegate for CPU.
[3166:3166:0409/165748.887422:ERROR:gpu_process_host.cc(1002)] GPU process exited unexpectedly: exit_code=139
[3166:3166:0409/165748.887451:FATAL:gpu_data_manager_impl_private.cc(448)] GPU process isn't usable. Goodbye.
[0409/165748.892463:ERROR:elf_dynamic_array_reader.h(64)] tag not found
[0409/165748.892533:ERROR:elf_dynamic_array_reader.h(64)] tag not found
[0409/165748.892607:ERROR:elf_dynamic_array_reader.h(64)] tag not found
[0409/165748.892710:ERROR:elf_dynamic_array_reader.h(64)] tag not found
Trace/breakpoint trap (core dumped)

Ok. No idea. I think both - chrome and slack - are 3rd party applications (binary only) with at least chrome heavily replacing all sorts of libs via LD_PRELOAD/LD_LIBRARY_PATH mechanism. No idea what they are exactly doing and how to address such issues then.

Chromium on Haswell seems fine here:
Chromium        122.0.6261.128 (openSUSE Build) stable (64-bit)
Revision        0000000000000000000000000000000000000000-0000000000000000000000000000000000000000
OS      Linux
JavaScript      V8 12.2.281.22
User Agent      Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/122.0.0.0 Safari/537.36
Command Line    /usr/bin/chromium-browser --flag-switches-begin --flag-switches-end --desktop-startup-id=msi85;1712700106;793478;4433_TIME2547330
Executable Path /usr/lib64/chromium/chrome-wrapper
Profile Path    /home/tst2000/.config/chromium/Default
Active Variations       f38ef081-ca7d8d80
# inxi -GSxxz
System:
  Kernel: 6.6.23-1-longterm arch: x86_64 bits: 64 compiler: gcc v: 13.2.1
  Desktop: KDE Plasma v: 5.27.10 tk: Qt v: 5.15.12 wm: kwin_x11 dm: 1: TDM
    2: XDM Distro: openSUSE Tumbleweed 20240407
Graphics:
  Device-1: Intel 4th Generation Core Processor Family Integrated Graphics
    vendor: Micro-Star MSI driver: i915 v: kernel arch: Gen-7.5 ports:
    active: HDMI-A-1,HDMI-A-2 empty: VGA-1 bus-ID: 00:02.0 chip-ID: 8086:041e
  Display: x11 server: X.Org v: 21.1.12 compositor: kwin_x11 driver: X:
    loaded: modesetting unloaded: fbdev,vesa alternate: intel dri: crocus
    gpu: i915 display-ID: :0 screens: 1
  Screen-1: 0 s-res: 2560x2490 s-dpi: 120
  Monitor-1: HDMI-A-1 mapped: HDMI-1 pos: top model: Dell P2213
    res: 1680x1050 dpi: 90 diag: 558mm (22")
  Monitor-2: HDMI-A-2 mapped: HDMI-2 pos: primary,bottom model: Acer K272HUL
    res: 2560x1440 dpi: 109 diag: 686mm (27")
  API: EGL v: 1.5 platforms: device: 0 drv: crocus device: 1 drv: swrast
    surfaceless: drv: crocus x11: drv: crocus inactive: gbm,wayland
  API: OpenGL v: 4.6 compat-v: 4.5 vendor: intel mesa v: 24.0.3 glx-v: 1.4
    direct-render: yes renderer: Mesa Intel HD Graphics 4400 (HSW GT2)
    device-ID: 8086:041e
  API: Vulkan v: 1.3.280 surfaces: xcb,xlib device: 0 type: integrated-gpu
    driver: N/A device-ID: 8086:041e
# rpm -qa | egrep 'vulk|intel|Mesa' | sort
intel-media-driver-24.1.3-1.2.x86_64
intel-vaapi-driver-2.4.1-5.13.x86_64
kernel-firmware-intel-20240322-2.1.noarch
libdrm_intel1-2.4.120-1.3.x86_64
libvulkan1-1.3.280.0-1.2.x86_64
libvulkan_intel-24.0.3-372.1.x86_64
Mesa-24.0.3-372.1.x86_64
Mesa-demo-egl-9.0.0-3.3.x86_64
Mesa-demo-es-9.0.0-3.3.x86_64
Mesa-demo-x-9.0.0-3.3.x86_64
Mesa-dri-24.0.3-372.1.x86_64
Mesa-gallium-24.0.3-372.1.x86_64
Mesa-libEGL1-24.0.3-372.1.x86_64
Mesa-libGL1-24.0.3-372.1.x86_64
Mesa-libglapi0-24.0.3-372.1.x86_64
Mesa-vulkan-device-select-24.0.3-372.1.x86_64
vulkan-tools-1.3.280.0-1.2.x86_64
#

This should be retested with Mesa 24.0.5 of current TW. There was a regression fixed users observed in 24.0.3.

(In reply to Stefan Dirsch from comment #9)
> This should be retested with Mesa 24.0.5 of current TW. There was a
> regression fixed users observed in 24.0.3.

Thanks! The issue got fixed on openSUSE Tumbleweed 20240508 with Mesa-24.0.5-373.1.x86_64.

Thanks for your positive feedback!