trismegisti
Can it be exploited? Considering the error messages, the possibility is high.
I don't like to see it as "Problem with the heap". As someone who played lots of CTF and is quite sufficient in exploiting such bugs, i would much rather see those things framed as "Problems with the glibc allocator".
If we just wouldn't use inline metadata, or verify it's integrity (smth like scudo but not broken), all of the security issues with the heap would just be gone. If you get to work with frameworks/languages that are more flexible when it comes to allocate memory (thinking about zig and it's amazing allocator abstraction here) you quickly realize that malloc and free are an insanely simplistic api for what is one of the most difficult and important problems in programming: memory allocation.
There is also no excuse for the error messages being that bad. Because the reality is that most systems programmers will have to debug those at some point.
This is HN and it would be cool to show support to the technical improvements and the security benefits of the whole wayland stack. Its fine if it is "no worky" for you. The goal is get it to work for everyone and actual reports on what does not work is much more helpful than philosophical arguments about wayland that have been ongoing for years.
Also you are not being forced to use it. Stick with i3, its fine.
I think there are already quite a few user benefits that come with wayland and for me wayland and XWayland works very well for all applications I use with the exception of some java guis. (that is also being worked on)
All of that beeing said, developing protocols and implementing them on multiple sides is just a slow process and we are not 100% there yet.