83dc5453c6
Xwayland initializes glamor on top of an EGL display, but some fatal
exit paths bypass the normal screen close sequence. In particular, this
can happen through xwl_give_up() after the Wayland compositor goes away,
or through ddxGiveUp() after early startup failures such as keymap
compilation failure.
A relevant excerpt from the ASan report:
Direct leak of 368 byte(s) in 1 object(s) allocated from:
#0 in calloc
#1 in dri2_display_create ../src/egl/drivers/dri2/egl_dri2.c:1014
#2 in dri2_initialize ../src/egl/drivers/dri2/egl_dri2.c:874
#3 in eglInitialize ../src/egl/main/eglapi.c:697
#4 in xwl_glamor_gbm_init_egl ../hw/xwayland/xwayland-glamor-gbm.c:1739
#5 in xwl_glamor_init ../hw/xwayland/xwayland-glamor.c:242
#6 in xwl_screen_init ../hw/xwayland/xwayland-screen.c:1121
#7 in AddScreen ../dix/dispatch.c:3999
#8 in InitOutput ../hw/xwayland/xwayland.c:437
#9 in dix_main ../dix/main.c:190
...
Direct leak of 32 byte(s) in 1 object(s) allocated from:
#0 in calloc
#1 in _eglCreateArray ../src/egl/main/eglarray.c:69
#2 in _eglLinkConfig ../src/egl/main/eglconfig.c:85
#3 in dri2_add_config ../src/egl/drivers/dri2/egl_dri2.c:457
#4 in drm_add_configs_for_visuals ../src/egl/drivers/dri2/platform_drm.c:563
#5 in dri2_initialize_drm ../src/egl/drivers/dri2/platform_drm.c:706
#6 in dri2_initialize ../src/egl/drivers/dri2/egl_dri2.c:892
#7 in eglInitialize ../src/egl/main/eglapi.c:697
...
|
||
|---|---|---|
| .gitlab-ci | ||
| composite | ||
| config | ||
| damageext | ||
| dbe | ||
| dix | ||
| doc | ||
| dri3 | ||
| exa | ||
| fb | ||
| glamor | ||
| glx | ||
| hw | ||
| include | ||
| man | ||
| mi | ||
| miext | ||
| os | ||
| present | ||
| pseudoramiX | ||
| randr | ||
| record | ||
| render | ||
| test | ||
| Xext | ||
| xfixes | ||
| Xi | ||
| xkb | ||
| .appveyor.yml | ||
| .dir-locals.el | ||
| .git-blame-ignore-revs | ||
| .gitignore | ||
| .gitlab-ci.yml | ||
| .mailmap | ||
| .travis.yml | ||
| COPYING | ||
| meson.build | ||
| meson_options.txt | ||
| README.md | ||
| SECURITY.md | ||
| 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: