Samsung Dealing With Wayland "Zombie Apocalypse" Bug

[MadCatX]

Okay, I know the need some sort of a fix that will work with the current rest of the stack but it sounds like a nasty kludge. It would be interesting to hear from the Wayland people if they intend to fix the protocol in the future.

[starshipeleven]

I would have thought that the solution would be to fix the protocol and force an update

we all know none does that in the embedded world.

When you can hack around the problem instead of fixing it, you do.

[boxie]

I felt the same, but I my guess is that the idea is to fix the issue in the protocol in the next (major?) version, but to supply a fix for the issue for clients of the existing version.

I would have thought that the solution would be to fix the protocol and force an update

[Azpegath]

I don't like to be negative, but this is starting to sound awfully cruft-accumulatory, which is supposed to be what Wayland was designed to avoid.

I felt the same, but I my guess is that the idea is to fix the issue in the protocol in the next (major?) version, but to supply a fix for the issue for clients of the existing version.

[PluMGMK]

I don't like to be negative, but this is starting to sound awfully cruft-accumulatory, which is supposed to be what Wayland was designed to avoid.

[paupav]

I've told you that Mir is the future.

[tildearrow]

Typo:

creating a zombie each time an object is instatiated and will live on past the object's lifespan.

[phoronix]

Phoronix: Samsung Dealing With Wayland "Zombie Apocalypse" Bug

Samsung OSG developers have been investigating and dealing with a nasty Wayland bug whereby a Wayland event could be delivered to an incorrect file descriptor. This ends up being due to a shortcoming in the Wayland protocol, but as to not break all existing software out there built against the current Wayland protocol, a workaround has been devised...

http://www.phoronix.com/scan.php?page=news_item&px=Samsung-Wayland-Zombie