Yet another reason we should bit the bullet at some point and switch our IPC story to proper XPC services with multiple executables on macOS: this wouldn't be a problem if we were using XPC objects.https://twitter.com/pcwalton/status/1172741450271903744 …
-
Show this thread
-
Replying to @nokusu
To be honest I think we should probably write a wrapper around Chromium’s Mojo and just let outsource all our IPC to Google. They even wrote Rust bindings :)
1 reply 0 retweets 0 likes -
Replying to @pcwalton
AFAIK, Mojo doesn't use XPC on macOS, so I have trouble believing it works without making shared IOSurface values global.
1 reply 0 retweets 0 likes -
Replying to @nokusu
I don’t think we need to transfer IOSurfaces between processes anymore?
1 reply 0 retweets 1 like -
Replying to @pcwalton
Oh, well if that's correct that certainly makes using XPC less important.
1 reply 0 retweets 0 likes
Replying to @nokusu
For security we don’t want the content process to be able to access GPU memory at all, including IOSurfaces. Too much driver attack surface.
0 replies
1 retweet
1 like
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.