-
-
Notifications
You must be signed in to change notification settings - Fork 593
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Crash when entering fullscreen in mpv if opacity value set for _NET_WM_STATE_HIDDEN
or _NET_WM_STATE_FULLSCREEN
#1350
Comments
can't reproduce on xfce. wm-specific? |
odd, can't reproduce on i3 either. can you build picom with asan enabled? that might give us more info. |
This is the output of picom when ASan is enabled:
|
hmm, looks like your picom is missing symbols. can you try again with the debug buildtype? |
oh, i have a hypothesis |
|
This is the output with debug buildtype:
|
Previously, if the type of a property changes, or if a number property went from inline (i.e. value->numbers) to external (i.e. value->array) or vice versa, we could leak allocated memory, or accessing the wrong member of a union (i.e. accessing value->array while value->numbers is active, or vice versa). Fixes #1350 Signed-off-by: Yuxuan Shui <yshuiv7@gmail.com>
thank you! can you try the |
Issue is no longer present with the |
Previously, if the type of a property changes, or if a number property went from inline (i.e. value->numbers) to external (i.e. value->array) or vice versa, we could leak allocated memory, or accessing the wrong member of a union (i.e. accessing value->array while value->numbers is active, or vice versa). Fixes #1350 Signed-off-by: Yuxuan Shui <yshuiv7@gmail.com>
Previously, if the type of a property changes, or if a number property went from inline (i.e. value->numbers) to external (i.e. value->array) or vice versa, we could leak allocated memory, or accessing the wrong member of a union (i.e. accessing value->array while value->numbers is active, or vice versa). Fixes #1350 Signed-off-by: Yuxuan Shui <yshuiv7@gmail.com>
Previously, if the type of a property changes, or if a number property went from inline (i.e. value->numbers) to external (i.e. value->array) or vice versa, we could leak allocated memory, or accessing the wrong member of a union (i.e. accessing value->array while value->numbers is active, or vice versa). Fixes #1350 Signed-off-by: Yuxuan Shui <yshuiv7@gmail.com>
Previously, if the type of a property changes, or if a number property went from inline (i.e. value->numbers) to external (i.e. value->array) or vice versa, we could leak allocated memory, or accessing the wrong member of a union (i.e. accessing value->array while value->numbers is active, or vice versa). Fixes #1350 Signed-off-by: Yuxuan Shui <yshuiv7@gmail.com>
Platform
Arch Linux amd64
GPU, drivers, and screen setup
AMD, single montitor
Environment
i3wm
picom version
v12.1
Diagnostics
[ 2024-10-09 22:22:35.919 egl_init WARN ] The egl backend is still experimental, use with care.
Version: v12.1 (/startdir/picom revision c321da4)
Extensions:
Misc:
(Another compositor is already running)
Drivers (inaccurate):
AMDGPU, Radeon
Backend: glx
Backend: egl
Configuration:
Configuration file
Steps of reproduction
_NET_WM_STATE_HIDDEN
or_NET_WM_STATE_FULLSCREEN
.Expected behavior
Picom should not crash when entering fullscreen in mpv.
Current Behavior
Prior to v12, I successfully used the following rules. With v12.1, these crashes picom with a fullscreen MPV window.
Stack trace
The text was updated successfully, but these errors were encountered: