Kwin effects restart when playing Terraria

Support KDE Plasma
1

So i have a pretty bizarre thing ive encountered, when playing Terraria (1.4.4.9) more and more frequently Kwin pretty much outright crashed my entire laptop, ill start it up play for not even 5 minutes and then the graphics will repeatedly reset until either terraria crashes itself or i have to force a shutdown by holding the power button, it used to happen every other hour and now i cant even play the game for 5 minutes. im thinking about switching the WM to something like compiz but if somehow this is fixed upstream i might switch to the testing branch, but id rather not have to move DEs entirely (or worse… install windows)

inxi output below

System:
  Kernel: 6.2.7-2-MANJARO arch: x86_64 bits: 64 compiler: gcc v: 12.2.1
    parameters: BOOT_IMAGE=/boot/vmlinuz-6.2-x86_64
    root=UUID=79290e4d-4b96-4c21-b8d2-2943a48596a3 rw quiet splash
    udev.log_priority=3 module_blacklist=hid_sensor_hub
  Desktop: KDE Plasma v: 5.26.5 tk: Qt v: 5.15.8 wm: kwin_x11 vt: 1 dm: SDDM
    Distro: Manjaro Linux base: Arch Linux
Machine:
  Type: Laptop System: Framework product: Laptop (12th Gen Intel Core) v: A4
    serial: <superuser required>
  Mobo: Framework model: FRANMACP04 v: A4 serial: <superuser required>
    UEFI: INSYDE v: 03.05 date: 08/23/2022
Battery:
  ID-1: BAT1 charge: 42.2 Wh (80.7%) condition: 52.3/55.0 Wh (95.1%)
    volts: 16.6 min: 15.4 model: NVT Framewo type: Li-ion serial: <filter>
    status: charging cycles: 4
Memory:
  RAM: total: 7.47 GiB used: 2.64 GiB (35.3%)
  RAM Report: permissions: Unable to run dmidecode. Root privileges required.
CPU:
  Info: model: 12th Gen Intel Core i5-1240P bits: 64 type: MST AMCP
    arch: Alder Lake level: v3 note: check built: 2021+
    process: Intel 7 (10nm ESF) family: 6 model-id: 0x9A (154) stepping: 3
    microcode: 0x41D
  Topology: cpus: 1x cores: 12 mt: 4 tpc: 2 st: 8 threads: 16 smt: enabled
    cache: L1: 1.1 MiB desc: d-8x32 KiB, 4x48 KiB; i-4x32 KiB, 8x64 KiB L2: 9 MiB
    desc: 4x1.2 MiB, 2x2 MiB L3: 12 MiB desc: 1x12 MiB
  Speed (MHz): avg: 1828 high: 2100 min/max: 400/4400:3300 scaling:
    driver: intel_pstate governor: powersave cores: 1: 2100 2: 2100 3: 2100
    4: 2100 5: 2100 6: 2100 7: 919 8: 2100 9: 2100 10: 1134 11: 1079 12: 2100
    13: 2100 14: 2100 15: 924 16: 2100 bogomips: 67600
  Flags: 3dnowprefetch abm acpi adx aes aperfmperf apic arat
    arch_capabilities arch_lbr arch_perfmon art avx avx2 avx_vnni bmi1 bmi2
    bts clflush clflushopt clwb cmov constant_tsc cpuid cpuid_fault cx16 cx8
    de ds_cpl dtes64 dtherm dts epb ept ept_ad erms est f16c flexpriority
    flush_l1d fma fpu fsgsbase fsrm fxsr gfni hfi ht hwp hwp_act_window
    hwp_epp hwp_notify hwp_pkg_req ibpb ibrs ibrs_enhanced ibt ida intel_pt
    invpcid invpcid_single lahf_lm lm mca mce md_clear mmx monitor movbe
    movdir64b movdiri msr mtrr nonstop_tsc nopl nx ospke pae pat pbe pcid
    pclmulqdq pdcm pdpe1gb pebs pge pku pln pni popcnt pse pse36 pts rdpid
    rdrand rdseed rdtscp rep_good sdbg sep serialize sha_ni smap smep smx
    split_lock_detect ss ssbd sse sse2 sse4_1 sse4_2 ssse3 stibp syscall tm
    tm2 tpr_shadow tsc tsc_adjust tsc_deadline_timer tsc_known_freq umip vaes
    vme vmx vnmi vpclmulqdq vpid waitpkg x2apic xgetbv1 xsave xsavec xsaveopt
    xsaves xtopology xtpr
  Vulnerabilities:
  Type: itlb_multihit status: Not affected
  Type: l1tf status: Not affected
  Type: mds status: Not affected
  Type: meltdown status: Not affected
  Type: mmio_stale_data status: Not affected
  Type: retbleed status: Not affected
  Type: spec_store_bypass mitigation: Speculative Store Bypass disabled via
    prctl
  Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer
    sanitization
  Type: spectre_v2 mitigation: Enhanced IBRS, IBPB: conditional, RSB
    filling, PBRSB-eIBRS: SW sequence
  Type: srbds status: Not affected
  Type: tsx_async_abort status: Not affected
Graphics:
  Device-1: Intel Alder Lake-P Integrated Graphics driver: i915 v: kernel
    arch: Gen-12.2 process: Intel 10nm built: 2021-22+ ports: active: eDP-1
    empty: DP-1, DP-2, DP-3, DP-4 bus-ID: 00:02.0 chip-ID: 8086:4626
    class-ID: 0300
  Display: x11 server: X.Org v: 21.1.7 compositor: kwin_x11 driver: X:
    loaded: modesetting alternate: fbdev,vesa dri: iris gpu: i915 display-ID: :0
    screens: 1
  Screen-1: 0 s-res: 2256x1504 s-dpi: 96 s-size: 596x397mm (23.46x15.63")
    s-diag: 716mm (28.19")
  Monitor-1: eDP-1 model: BOE Display 0x095f built: 2019 res: 2256x1504
    hz: 60 dpi: 201 gamma: 1.2 size: 285x190mm (11.22x7.48") diag: 343mm (13.5")
    ratio: 3:2 modes: 2256x1504
  API: OpenGL v: 4.6 Mesa 22.3.5 renderer: Mesa Intel Graphics (ADL GT2)
    direct-render: Yes
Audio:
  Device-1: Intel Alder Lake PCH-P High Definition Audio driver: snd_hda_intel
    v: kernel alternate: snd_sof_pci_intel_tgl bus-ID: 00:1f.3 chip-ID: 8086:51c8
    class-ID: 0403
  Sound API: ALSA v: k6.2.7-2-MANJARO running: yes
  Sound Server-1: JACK v: 1.9.22 running: no
  Sound Server-2: PulseAudio v: 16.1 running: yes
  Sound Server-3: PipeWire v: 0.3.65 running: yes
Network:
  Device-1: Intel Wi-Fi 6 AX210/AX211/AX411 160MHz driver: iwlwifi v: kernel
    pcie: gen: 2 speed: 5 GT/s lanes: 1 bus-ID: a6:00.0 chip-ID: 8086:2725
    class-ID: 0280
  IF: wlp166s0 state: up mac: <filter>
  IP v4: <filter> type: dynamic noprefixroute scope: global
    broadcast: <filter>
  IP v6: <filter> type: noprefixroute scope: link
  WAN IP: <filter>
Bluetooth:
  Device-1: Intel AX210 Bluetooth type: USB driver: btusb v: 0.8 bus-ID: 3-10:5
    chip-ID: 8087:0032 class-ID: e001
  Report: rfkill ID: hci0 rfk-id: 0 state: up address: see --recommends
Logical:
  Message: No logical block device data found.
RAID:
  Message: No RAID data found.
Drives:
  Local Storage: total: 1.14 TiB used: 129.88 GiB (11.1%)
  SMART Message: Unable to run smartctl. Root privileges required.
  ID-1: /dev/nvme0n1 maj-min: 259:0 vendor: Samsung model: MZVLW256HEHP-00000
    size: 238.47 GiB block-size: physical: 512 B logical: 512 B speed: 31.6 Gb/s
    lanes: 4 type: SSD serial: <filter> rev: CXB7401Q temp: 36.9 C scheme: GPT
  ID-2: /dev/sda maj-min: 8:0 type: USB model: USB DISK 3.2 size: 931.51 GiB
    block-size: physical: 512 B logical: 512 B type: N/A serial: <filter>
    rev: PMAP scheme: MBR
  SMART Message: Unknown USB bridge. Flash drive/Unsupported enclosure?
  Message: No optical or floppy data found.
Partition:
  ID-1: / raw-size: 60 GiB size: 58.76 GiB (97.93%) used: 14.37 GiB (24.5%)
    fs: ext4 dev: /dev/nvme0n1p2 maj-min: 259:2 label: root
    uuid: 79290e4d-4b96-4c21-b8d2-2943a48596a3
  ID-2: /boot/efi raw-size: 300 MiB size: 299.4 MiB (99.80%)
    used: 312 KiB (0.1%) fs: vfat dev: /dev/nvme0n1p1 maj-min: 259:1 label: EFI
    uuid: B154-7629
  ID-3: /home raw-size: 170 GiB size: 166.27 GiB (97.81%)
    used: 22.98 GiB (13.8%) fs: ext4 dev: /dev/nvme0n1p3 maj-min: 259:3
    label: home uuid: ae6db027-44f0-4ade-8c30-311e06198026
  ID-4: /mnt/sda1 raw-size: 931.51 GiB size: 915.82 GiB (98.32%)
    used: 92.53 GiB (10.1%) fs: ext4 dev: /dev/sda1 maj-min: 8:1 label: 1TB-SSD
    uuid: 785bbd29-d275-4cd7-af25-49534ffcb894
Swap:
  Kernel: swappiness: 60 (default) cache-pressure: 100 (default)
  ID-1: swap-1 type: partition size: 8.17 GiB used: 0 KiB (0.0%) priority: -2
    dev: /dev/nvme0n1p4 maj-min: 259:4 label: swap
    uuid: 0bbd3775-8a80-4174-8136-463be6b47961
Unmounted:
  Message: No unmounted partitions found.
USB:
  Hub-1: 1-0:1 info: Hi-speed hub with single TT ports: 1 rev: 2.0
    speed: 480 Mb/s chip-ID: 1d6b:0002 class-ID: 0900
  Hub-2: 2-0:1 info: Super-speed hub ports: 4 rev: 3.1 speed: 20 Gb/s
    chip-ID: 1d6b:0003 class-ID: 0900
  Device-1: 2-4:2 info: Kingston USB DISK 3.2 type: Mass Storage driver: uas
    interfaces: 1 rev: 3.2 speed: 10 Gb/s power: 896mA chip-ID: 13fe:6500
    class-ID: 0806 serial: <filter>
  Hub-3: 3-0:1 info: Hi-speed hub with single TT ports: 12 rev: 2.0
    speed: 480 Mb/s chip-ID: 1d6b:0002 class-ID: 0900
  Device-1: 3-3:2 info: Framework HDMI Expansion Card type: Billboard,HID
    driver: hid-generic,usbhid interfaces: 2 rev: 2.0 speed: 12 Mb/s power: 100mA
    chip-ID: 32ac:0002 class-ID: 0300 serial: <filter>
  Device-2: 3-4:3 info: SHARKOON GmbH [Mediatrack Edge Mini Keyboard]
    type: Keyboard,Mouse driver: hid-generic,usbhid interfaces: 2 rev: 1.1
    speed: 12 Mb/s power: 100mA chip-ID: 1ea7:0066 class-ID: 0301
  Device-3: 3-9:4 info: Shenzhen Goodix USB2.0 MISC type: <vendor specific>
    driver: N/A interfaces: 1 rev: 2.0 speed: 12 Mb/s power: 100mA
    chip-ID: 27c6:609c class-ID: ef00 serial: <filter>
  Device-4: 3-10:5 info: Intel AX210 Bluetooth type: Bluetooth driver: btusb
    interfaces: 2 rev: 2.0 speed: 12 Mb/s power: 100mA chip-ID: 8087:0032
    class-ID: e001
  Hub-4: 4-0:1 info: Super-speed hub ports: 4 rev: 3.1 speed: 10 Gb/s
    chip-ID: 1d6b:0003 class-ID: 0900
Sensors:
  System Temperatures: cpu: 42.0 C mobo: N/A
  Fan Speeds (RPM): N/A
Info:
  Processes: 313 Uptime: 14m wakeups: 1951 Init: systemd v: 252
  default: graphical tool: systemctl Compilers: gcc: 12.2.1 clang: 15.0.7
  Packages: pm: pacman pkgs: 1391 libs: 425 tools: pamac Shell: Zsh v: 5.9
  default: Bash v: 5.1.16 running-in: konsole inxi: 3.3.25
2

Welp, it was not a kwin issue, it seems to have been an issue with terraria running on intel igpus, ill close this for now but if anyone else stumbles this way, try changing the lighting options to something different, white seems to work for me.

3

It appears that this is does not fix the issue on my end, as its now back as a recurring issue (it worked for a while last night and now its not)

4

Im beginning to think its just a terraria issue that seems amplified with KDEs kwin? or at least it causes kwin to crash and burn, i moved to the testing branch as well as just running it in proton with d9vk/dxvk enabled in the launch settings for steam. im hoping something somewhere in either KDE/kwin or terraria is just fixed now but who can really say at this point.

5
6

i appreciate this i didnt even know this was a thing, but if the keyboard gets locked up along with the display (happened on several occasions for me) its kinda useless.

7

Unfortunately it is not always an option, but in 99% of lock-up situations it will still work. There are many more parts of the computer still chugging during a crash than you realize, and SysRq goes to the lowest parts of your system. I suggest at least trying it when your computer crashes before resorting to something else.

8

Alright, ill give it a shot next time. Thank you