8707d2835c
Currently, Xwayland creates a pixmap backed by shared memory buffer as soon as an X11 cursor is realized, which is destroyed when the cursor is eventually unrealized. If an X11 client is leaking cursors, Xwayland will be creating new pixmaps continuously, which will eventually cause an error once the limit is reached, and get Xwayland killed. However, we do not need the shared memory buffer to stay around, we already have the buffer retention mechanism which will take care of keeping the buffer around until the Wayland compositor is done with it, so we could just create and destroy the pixmap as needed when setting the cursor. That would not fix the leak in the X11 application, yet that would mitigate the risk of Xwayland being killed by reaching the shared memory limits, until the client itself reaches the limit of X11 resources. v2: Don't increase the pixmap refcnt to destroy it just after (Michel) Signed-off-by: Olivier Fourdan <ofourdan@redhat.com> Suggested-by: Michel Dänzer <michel@daenzer.net> See-also: https://gitlab.freedesktop.org/xorg/xserver/-/issues/1773 Part-of: <https://gitlab.freedesktop.org/xorg/xserver/-/merge_requests/1754> |
||
|---|---|---|
| .gitlab-ci | ||
| Xext | ||
| Xi | ||
| composite | ||
| config | ||
| damageext | ||
| dbe | ||
| dix | ||
| doc | ||
| dri3 | ||
| exa | ||
| fb | ||
| glamor | ||
| glx | ||
| hw | ||
| include | ||
| man | ||
| mi | ||
| miext | ||
| os | ||
| present | ||
| pseudoramiX | ||
| randr | ||
| record | ||
| render | ||
| test | ||
| xfixes | ||
| xkb | ||
| .appveyor.yml | ||
| .dir-locals.el | ||
| .git-blame-ignore-revs | ||
| .gitignore | ||
| .gitlab-ci.yml | ||
| .mailmap | ||
| .travis.yml | ||
| COPYING | ||
| README.md | ||
| meson.build | ||
| meson_options.txt | ||
| xorg-server.m4 | ||
| xorg-server.pc.in | ||
| xserver.ent.in | ||
X Server
The X server accepts requests from client applications to create windows, which are (normally rectangular) "virtual screens" that the client program can draw into.
Windows are then composed on the actual screen by the X server (or by a separate composite manager) as directed by the window manager, which usually communicates with the user via graphical controls such as buttons and draggable titlebars and borders.
For a comprehensive overview of X Server and X Window System, consult the following article: https://en.wikipedia.org/wiki/X_server
All questions regarding this software should be directed at the Xorg mailing list:
https://lists.freedesktop.org/mailman/listinfo/xorg
The primary development code repository can be found at:
https://gitlab.freedesktop.org/xorg/xserver
For patch submission instructions, see:
https://www.x.org/wiki/Development/Documentation/SubmittingPatches
As with other projects hosted on freedesktop.org, X.Org follows its Code of Conduct, based on the Contributor Covenant. Please conduct yourself in a respectful and civilized manner when using the above mailing lists, bug trackers, etc: