-
-
Notifications
You must be signed in to change notification settings - Fork 585
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
backend: dummy: do not leak owned pixmaps #1022
backend: dummy: do not leak owned pixmaps #1022
Conversation
Codecov Report
@@ Coverage Diff @@
## next #1022 +/- ##
==========================================
+ Coverage 37.58% 37.59% +0.01%
==========================================
Files 49 49
Lines 11155 11160 +5
==========================================
+ Hits 4193 4196 +3
- Misses 6962 6964 +2
|
it works kinda weird with the root back pixmap and i can't figure out why 🤔 |
how weird? |
iirc,
do you have any ideas what could cause such behavior? i didn't have much time to investigate when i encountered this issue. btw, i'm alive, just a bit short on time. i should be able to dedicate a lot of time to picom soon 🙂 |
i have an idea! looks like it's about pixmap ownership controlled by the |
4e243c3
to
f973278
Compare
exactly. now the fix is complete. |
"reisze_region" => "resize_region"
free pixmaps which ownership was transferred to the backend
f973278
to
223872b
Compare
fix a typo and an issue reported by xrescheck: