XWayland Lands Fix For At Least One Game Hanging It & Causing 100% CPU Usage

[oiaohm]

The two changes aren't directly related. The glamor flush one is just a minor performance optimization.

Also, I hate to interrupt the deluge of off-topic posts with some on-topic stuff, but the bug fixed by my change seems really hard to hit. Even the GitLab issue reporter wasn't able to reproduce it anymore, even without any fix. Xwayland 22.1 already had the issue, but we didn't get any other reports.

https://steamcommunity.com/app/221040/discussions/0/43099721782055267/

Resident Evil 6 is a touchy bit of software even under Windows over the years. Minor performance optimizations can be the difference between if Resident Evil 6 goes into dive off cliff and consume the CPU like mad or not. If it triggers or not depends on what patches are applied to Resident Evil 6.

Resident Evil 6 bugs are a total pain in the tail to reproduce for wine and proton developers.

https://steamdb.info/app/221040/patchnotes/

Do note the 28 February 2023 patch.

[oiaohm]

It seems you mistook me with yourself, liar.

No both of you are liars but the type of lie neither of you at first are going to notice you have done it.

https://www.phoronix.com/forums/forum/linux-graphics-x-org-drivers/wayland-display-server/1380218-xwayland-lands-fix-for-at-least-one-game-hanging-it-causing-100-cpu-usage?p=1380419#post1380419

Both of you incorrectly presume that your experiences told you how Linux is.

[Ironmask]

Both of you incorrectly presume that your experiences told you how Linux is.

I mostly find it depressing that people consider one or the other some sort of messiah instead of just a tool.
Operating systems are complex systems that are responsible for operating a wide range of competing and incompatible hardware. Due to society's innate rejection of assisting each other, it's inevitable that software has to bear the brunt of that lack of cooperation. Design hardly matters, what matters is how well the stack works together, and how the stack targets particular hardware.

[HEL88]

It seems you mistook me with yourself, liar.

You are not intelligent if you think I took myself to be a Linux troll.

You even stupidly lie when you write that Linux has never failed you - but I know, you act like a fan of a football team or a fan of car brands like BMW or Honda - never a bad word about the worshipped object.

And I was a huge windows fan!

.

But as you wrote earlier: you were a huge Windows fan, and now you are a Linux fan.

Such users are always the worst - they hate the former objects of their desire, and spill their venom on the forums.

[oiaohm]

You even stupidly lie when you write that Linux has never failed you

No this is one of the classic presumes. I have a time frame of 8 years where I did not have a Linux failure. But I have been using Linux for over 22 years.

So its not impossible for someone to dream run and I know that from personal experience.

With the number of Linux users there are going to be some of them who have dream runs. I was lucky in some ways that I did not start out using Linux with a dream run.

Yes people have dream runs with Mac OS and Windows as well. This is status normal percentage of users of any of the main OS options will use it and not have a single recall-able issue sometimes for over a decade.

[oiaohm]

I mostly find it depressing that people consider one or the other some sort of messiah instead of just a tool.
Operating systems are complex systems that are responsible for operating a wide range of competing and incompatible hardware. Due to society's innate rejection of assisting each other, it's inevitable that software has to bear the brunt of that lack of cooperation. Design hardly matters, what matters is how well the stack works together, and how the stack targets particular hardware.

Its way more complex than that. I will give a horrible example. Most people will think libreoffice will operate fine on Raspberry pi 4 8G running linux. I have a single document that if you open on libreoffice on a Raspberry Pi4 that will cause the GPU to overload it because it uses a particular feature of fontwork. So 99.99% libreoffice works without issue. Its the full donuts/circular fontwork with lots of text in it that will fairly much always bring Raspberry pi 4 8G to the ground.

Yes how a stack targets particular hardware is important but it also what the software the user will want to use will demand out the hardware. This is one of the catches a stack might have particular issues but they don't matter to large group of users because they never use the features in software that trigger those issues.

The dream run trap. It possible to be using combination of software with combination of hardware that you are not seeing the hardware or stack issues.

I do agree with you that people take OS as messiah way too often. Its really hard to accept that every where know about OS from personal usage is biased on how we use software. Horrible a person can be having a completely different outcome performing the same task with the same software just because they are traveling though the interface differently.

Ironmask the horrible reality once you look deeper at this problem you end up coming to the horrible reality there that is no real way to be sure how well a stack works with particular hardware even using benchmarks there are just too many options.

Over 20 years using Linux, Windows and Mac OS you kind of grow out some of these self deceptions.

We don't have clean compare lists of operating systems because due to the complexity you cannot make them without bias.

[MrCooper]

Resident Evil 6 is a touchy bit of software even under Windows over the years. Minor performance optimizations can be the difference between if Resident Evil 6 goes into dive off cliff and consume the CPU like mad or not.

That's interesting, probably not directly related to this issue though, which was an infinite loop in Xwayland.

[oiaohm]

That's interesting, probably not directly related to this issue though, which was an infinite loop in Xwayland.

It is kind of related because it a case of two infinite loop sources and in different places. There is a catch here Resident Evil 6 has watchdog for infinite loop detection. I don't know if the Xwayland bug can be got around by the client side application detect it stalled so redoing connection to xwayland because it thinks it self is stalled.

History of Resident Evil having infinite loop problems in it own code and protections against that added to the game might be something else undermining the repeatability of the bug.

[MrCooper]

I don't know if the Xwayland bug can be got around by the client side application detect it stalled so redoing connection to xwayland because it thinks it self is stalled.

It cannot. The xserver code is single threaded, an infinite loop means the X server stops responding to clients. The only way out is killing it (which in the case of Xwayland may or may not take down the Wayland compositor as well).