<html>
<head>
<base href="https://bugs.freedesktop.org/" />
</head>
<body><table border="1" cellspacing="0" cellpadding="8">
<tr>
<th>Priority</th>
<td>medium
</td>
</tr>
<tr>
<th>Bug ID</th>
<td><a class="bz_bug_link
bz_status_NEW "
title="NEW --- - wl_data_device lacks destructor protocol, causes leaks"
href="https://bugs.freedesktop.org/show_bug.cgi?id=81745">81745</a>
</td>
</tr>
<tr>
<th>Assignee</th>
<td>wayland-bugs@lists.freedesktop.org
</td>
</tr>
<tr>
<th>Summary</th>
<td>wl_data_device lacks destructor protocol, causes leaks
</td>
</tr>
<tr>
<th>Severity</th>
<td>major
</td>
</tr>
<tr>
<th>Classification</th>
<td>Unclassified
</td>
</tr>
<tr>
<th>OS</th>
<td>All
</td>
</tr>
<tr>
<th>Reporter</th>
<td>ppaalanen@gmail.com
</td>
</tr>
<tr>
<th>Hardware</th>
<td>All
</td>
</tr>
<tr>
<th>Status</th>
<td>NEW
</td>
</tr>
<tr>
<th>Version</th>
<td>1.5.0
</td>
</tr>
<tr>
<th>Component</th>
<td>wayland
</td>
</tr>
<tr>
<th>Product</th>
<td>Wayland
</td>
</tr></table>
<p>
<div>
<pre>wl_data_device interface does not have a destructor defined in the protocol,
which means that the server cannot know if a client destroys a wl_data_device
object. This leaks the server-side resource.
To make things worse, wl_data_device.data_offer *event* creates a new
wl_data_offer protocol object.
If a client has destroyed a wl_data_device, the server will not know about it,
and will keep sending data_offer events as appropriate. As the client does not
track the wl_data_device object anymore, those events will be ignored in the
client. This means that in the server, wl_data_offer objects just keep piling
up, as the server cannot destroy them on its own.
If possible, we should add destructor protocol to wl_data_device interface.</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the assignee for the bug.</li>
</ul>
</body>
</html>