On 03/31/2015 11:26 AM, Derek Foreman wrote:
Some compositors perform rendering in a separate thread. If a client
destroy occurs during rendering a segfault will occur when the client's
shared memory pools are unmapped and the renderer continues to use them.
Is this thing correctly handling th
Some compositors perform rendering in a separate thread. If a client
destroy occurs during rendering a segfault will occur when the client's
shared memory pools are unmapped and the renderer continues to use them.
This adds a way (disabled by default) to queue shared memory pool deletion
instead
