00:04 <mstoeckl> whoever controls wlb: it doesn't currently report wayland-util issues/merge requests

07:31 <dottedmag> Do libwayland (wlroots?) limit amount of IDs created by a client beyond 0xfeffffff limit?

16:46 <mstoeckl> dottedmag: wl_proxy_create calls wl_map_insert_new, which has no limiting logic

16:49 <mstoeckl> however, to hit the client ID limit, you need to have store all 4.2e9 intervening IDs, which takes ~90 bytes object, so 360GB of memory

17:09 <wlb> wayland Merge request !167 opened by M. Stoeckl (mstoeckl) client: handle fcntl error in wl_display_connect https://gitlab.freedesktop.org/wayland/wayland/-/merge_requests/167

19:04 <dottedmag> mstoeckl: Yeah, I was thinking about client requesting tons of IDs, thus making the server suffer. But probably that's not the only way to make the server suffer anyway.

19:31 <mstoeckl> dottedmag: have you seen https://github.com/emersion/wleird/blob/master/resource-thief.c :-)

19:35 <mstoeckl> also, a 15-line Python script sending 'wl_display.sync' can put the entire cost of allocations solely on the server

20:12 <kennylevinsen> Maybe compositors should just enforce, idk, 4k objects per client...

21:54 <|> erp