ChanServ changed the topic of #wayland to: https://wayland.freedesktop.org | Discussion about the Wayland protocol and its implementations, plus libinput
Drakulix has quit [Ping timeout: 480 seconds]
Drakulix has joined #wayland
Hypfer has quit [Ping timeout: 480 seconds]
bindu_ has quit [Ping timeout: 480 seconds]
bindu has joined #wayland
feaneron has quit [Read error: Connection reset by peer]
dcz_ has joined #wayland
Tom^ has quit [Remote host closed the connection]
eroc1990 has quit [Quit: Ping timeout (120 seconds)]
eroc1990 has joined #wayland
dcz_ has quit [Quit: Konversation terminated!]
dcz_ has joined #wayland
Company has quit [Ping timeout: 480 seconds]
feaneron has joined #wayland
dcz_ has quit [Quit: Konversation terminated!]
alarumbe has quit []
Company has joined #wayland
garnacho has quit [Ping timeout: 480 seconds]
Drakulix has quit [Ping timeout: 480 seconds]
kestrel has quit [Read error: Connection reset by peer]
feaneron has quit [Remote host closed the connection]
dcz_ has joined #wayland
Drakulix has quit [Ping timeout: 480 seconds]
garnacho has joined #wayland
sima has joined #wayland
coldfeet has quit [Quit: Lost terminal]
Drakulix has joined #wayland
kekekeks has quit [Ping timeout: 480 seconds]
Drakulix has quit [Ping timeout: 480 seconds]
kekekeks has joined #wayland
Drakulix has joined #wayland
kekekeks has quit [Ping timeout: 480 seconds]
Calandracas has joined #wayland
Calandracas_ has quit [Ping timeout: 480 seconds]
kekekeks has joined #wayland
crombie has joined #wayland
crombie has quit [Ping timeout: 480 seconds]
crombie has joined #wayland
fatal has quit [Ping timeout: 480 seconds]
rasterman has joined #wayland
fatal has joined #wayland
fatal has quit [Remote host closed the connection]
dcz_ has quit [Read error: Connection reset by peer]
fatal has joined #wayland
dcz_ has joined #wayland
fmuellner has joined #wayland
alarumbe has joined #wayland
Guest16412 has quit [Ping timeout: 480 seconds]
notfunderscore has joined #wayland
Moprius has joined #wayland
Moprius has quit []
Company has joined #wayland
fmuellner has quit []
fmuellner has joined #wayland
Moprius has joined #wayland
eroc1990 has joined #wayland
karenw has quit [Ping timeout: 480 seconds]
vyivel has quit [Remote host closed the connection]
vyivel has joined #wayland
nerdopolis has joined #wayland
iomari891 has joined #wayland
karenw has joined #wayland
Drakulix has quit [Ping timeout: 480 seconds]
alatiera4 has joined #wayland
alatiera has quit [Ping timeout: 480 seconds]
alatiera4 is now known as alatiera
Drakulix has joined #wayland
nerdopolis has quit [Ping timeout: 480 seconds]
nniro has quit [Ping timeout: 480 seconds]
Ps1-Jack has quit [Ping timeout: 480 seconds]
feaneron has joined #wayland
Drakulix has quit [Ping timeout: 480 seconds]
notfunderscore is now known as funderscore
Psi-Jack has joined #wayland
Drakulix has joined #wayland
karenw has quit [Ping timeout: 480 seconds]
dcz_ has quit [Quit: Konversation terminated!]
nerdopolis has joined #wayland
feaneron has quit [Read error: Connection reset by peer]
coldfeet has joined #wayland
x01bee has joined #wayland
x01bee has quit [Remote host closed the connection]
coldfeet has quit [Quit: Lost terminal]
garnacho has quit [Quit: garnacho]
garnacho has joined #wayland
<kekekeks>
What happens to new_id wl_proxy objects from events if an event listener/dispatcher was never added? Do they leak?
<kekekeks>
Is it mandatory to set a listener immediately after proxy creation?
Drakulix has quit [Ping timeout: 480 seconds]
<kekekeks>
Yep, proxies seem to be leaking
Drakulix has joined #wayland
<kekekeks>
A wl_proxy_add_listener being mandatory to call for every proxy with events doesn't seem to documented anywhere.
fatal has quit [Remote host closed the connection]
fatal has joined #wayland
<kekekeks>
A possible scenario where that's relevant would be a client that's only concerned about initiating drag-n-drop and providing clipboard data and not about reading it. So it would make sense for such an app to skip subscribing to events originating from wl_data_device.
<kekekeks>
This would cause a memory leak on both the client and the compositor (since it needs to track object ids)
<Consolatis>
only for the lifetime of the client application though
<kekekeks>
Still an undocumented memory leak
<Consolatis>
true
<Consolatis>
not installing a listener is also the only option to not have a set of dummy functions with the right signature just to ignore the events anyway
<Consolatis>
from memory at least, providing NULL pointers in a event listener makes libwayland go mad
<kekekeks>
it will attempt to call a null pointer if you provide it in your listener function table, yes
<kekekeks>
but that's a separate thing and I'd consider it to be expected
<kekekeks>
>just to ignore the events anyway
<kekekeks>
One can't ignore events with new_id arguments, that's the point
<kekekeks>
The moment libwayland attempts to dispatch such an event, the original wl_proxy "owner" becomes the "owner" of that newly created proxy
<kekekeks>
but it's not documented anywhere that not specifying a listener at all leads to memory leaks
<Consolatis>
^ right, but there are also other cases where one is only interested in very specific events and not all of them. that is indeed a separate issue though
<Consolatis>
i'd expect most (if not all) clients to handle new_id events because that usually is what they created the parent object for
<kekekeks>
Well, an example from the core wayland.xml protocol is wl_data_device that's needed for initiating drag-n-drops, but client doesn't neccessary accepts those
<kekekeks>
I'm sure there are similar cases with other protocols
crombie has quit [Ping timeout: 480 seconds]
<linkmauve>
kekekeks, oh I wanted to reply to you the other day, have you had a look at GtkGraphicsOffload already, which seems to do at least parts of what you want?
Drakulix has quit [Ping timeout: 480 seconds]
leon-anavi has quit [Quit: Leaving]
Drakulix has joined #wayland
<kekekeks>
Is it possible to present surfaces from a dedicated thread while UI thread is busy?
<kekekeks>
Our toolkit's rendering model uses a dedicated thread for rendering and allows one to define animations or custom render tree nodes that continue ticking and rendering even if UI thread is stuck in e. g. sleep(1)
Drakulix_ has joined #wayland
Drakulix has quit [Ping timeout: 480 seconds]
Drakulix_ is now known as Drakulix
Drakulix has quit [Ping timeout: 480 seconds]
Drakulix has joined #wayland
rasterman has quit [Quit: Gettin' stinky!]
feaneron has joined #wayland
kasper93 has quit []
kasper93 has joined #wayland
sima has quit [Ping timeout: 480 seconds]
eroc1990 has quit [Read error: Connection reset by peer]
bindu has quit [Remote host closed the connection]
bindu has joined #wayland
Moprius has quit []
feaneron has quit [Remote host closed the connection]