Skip to content

Silence some LeakSanitizer warnings

Simon McVittie requested to merge smcv/dbus:leak-sanitizer into master

  • test-privserver: Don't leak a copy of the server address

  • test-privserver: Move cleanup of DBusLoop into test_service_data_free()

  • test-privserver: Exit if DBusLoop cannot be allocated

    Otherwise, we'd just crash when we dereference the null pointer.

  • dbus-launch-x11: Ignore X11 connection when checking for memory leaks

    The X11 connection is opened and never closed. Because dbus-launch forks and continues to run non-trivial code in a forked child, it is not clear whether (or where) it would be safe to close it; instead, we leave it open until process exit, at which point the socket is cleaned up by the kernel.

    Any memory allocated for the X11 connection is only allocated once per run of dbus-launch, so there's no need to keep track of it, and we can silence these memory leak warnings as uninteresting.

Merge request reports