Open TheConfuZzledDude opened 4 years ago
Can you set --log-level=debug
and upload the log file here?
Also, it doesn't seem to crash when --experimental-backends isn't specified, but it does still break the compositing, and produces a weird ghosting effect, which may be related?
Ah, sorry, I need a little bit more information. Can you do these:
meson configure --buildtype=debug
)--log-level=debug
, and trigger the crash again (sorry)picom
executable, the log file, and the coredump (you can find where the coredump is by using coredumpctl)Hopefully this is good, I meant to upload the core dump initially but I got sidetracked haha picom-debugging.zip
I was with this problem too, so I've installed picom-ibhagwan-git
to use dual kawase blur and I notice that after reloading i3, the blur crashes (but picom keep running).
To do a workaround for this, I made a script to execute always in reloading i3
#!/usr/bin/env bash
killall -e picom
while pgrep -u $UID -x picom > /dev/null; do sleep 1; done
picom --experimental-backends -b
I think I've found a fix/workaround for a possibly duplicate issue https://github.com/yshui/picom/issues/394.
Can you try if this PR https://github.com/yshui/picom/pull/479 also fixes the assertion failure for you?
Platform
Arch Linux 5.6.6-13-tkg-pds
GPU, drivers, and screen setup
AMD RX 5700XT and AMD R9 290 (the 5700XT is the one doing all the rendering), dual monitors. mesa-aco-git 20.1.0_devel.20200424.961f041f957-1, and xf86-video-amdgpu 19.1.0-1
Environment
i3-gaps-next-git 4.18.r19.g15fef832-1
picom version
Version: vgit-0b377
Extensions:
Misc:
Drivers (inaccurate):
AMDGPU, Radeon
Configuration:
Steps of reproduction
picom --experimental-backends
Expected behavior
Picom reloads without any issues
Current Behavior
Picom segfaults
Stack trace
Error on crash is picom: ../src/backend/backend.c:270: paint_all_new: Assertion `!(w->flags & WIN_FLAGS_SHADOW_NONE)' failed. [1] 86842 abort (core dumped) picom --experimental-backends
Other details