Mir

mir:more-aggressively-release-buffers

  1. Git
  2. lp:mir
  3. more-aggressively-release-buffers
Last commit made on 2020-09-04
Get this branch:
git clone -b more-aggressively-release-buffers https://git.launchpad.net/mir

Branch merges

Branch information

Name:
more-aggressively-release-buffers
Repository:
lp:mir

Recent commits

101d02a... by Chris Halse Rogers

renderer: More aggressively release client buffers

2583bfb... by "bors[bot]" <26634292+bors[bot]@users.noreply.github.com>

Merge #1691

1691: gbm-kms: Enable more GL debugging for --debug r=AlanGriffiths a=RAOF

This sets up a debug GL context, which drivers will generally use to do more checks and output more verbose messages, and installs a maximally-verbose GL debug logging callback to catch those messages.

Co-authored-by: Christopher James Halse Rogers <email address hidden>

72c78ec... by Chris Halse Rogers

tests/MockEGL: Handle libepoxy `dlopen`ing libEGL.

libepoxy dynamically loads libEGL, so our mocks in mock_egl.cpp aren't
used by calls through epoxy. (epoxy *also* `dlopen`s libGL/GLES, but
that's not a problem for now).

Add a `dlopen` interposer to catch attempts to load `libEGL.so.1` and
resolve them to the test binary instead so that the mock entrypoints
are used.

9ab1ca8... by Chris Halse Rogers

gbm-kms: Only enable GL debug when debugging is enabled

7bd808b... by "bors[bot]" <26634292+bors[bot]@users.noreply.github.com>

Merge #1692

1692: Send wl_touch.up() and wl_keyboard.leave() events when surface destroyed r=AlanGriffiths a=wmww

We already send a `wl_pointer.leave()` event using this same method, but we were not sending `wl_touch.up()` and `wl_keyboard.leave()`. The former is tested by https://github.com/MirServer/wlcs/pull/177. The latter fixes #1236.

Co-authored-by: William Wold <email address hidden>

09ab65a... by William Wold <email address hidden>

Addressed review

c2c7bab... by "bors[bot]" <26634292+bors[bot]@users.noreply.github.com>

Merge #1693

1693: Log SIGHUP and other signals r=Saviq a=AlanGriffiths

Some deployments are sending Mir a SIGHUP that was causing us to exit untidily.

Explicitly handle SIGHUP and log all signal.

Co-authored-by: Alan Griffiths <email address hidden>

8e84d3d... by Alan Griffiths

Don't ignore SIGHUP, but do log it

4dd17bc... by Alan Griffiths

Ignore SIGHUP

def4757... by William Wold <email address hidden>

Send wl_keyboard.leave() when surface destroyed