> if it was easy to fix, some of the "big players" (Apple, Google, KDE, Opera...)
> would have already done that.

These "big players" don't use WebKit1 anymore anyway but WebKit2 or Blink*, so their browsers are not affected. There is no incentive for them to fix this WebKit1 issue at hand, whether they are able to or not.

* Blink itself doesn't have multi-process architecture, but existing browsers using Blink implement this feature at browser level instead of engine level.