Skip to content
By using Twitter’s services you agree to our Cookies Use. We and our partners operate globally and use cookies, including for analytics, personalisation, and ads.

This is the legacy version of twitter.com. We will be shutting it down on June 1, 2020. Please switch to a supported browser, or disable the extension which masks your browser. You can see a list of supported browsers in our Help Center.

  • Home Home Home, current page.
  • About

Saved searches

  • Remove
  • In this conversation
    Verified accountProtected Tweets @
Suggested users
  • Verified accountProtected Tweets @
  • Verified accountProtected Tweets @
  • Language: English
    • Bahasa Indonesia
    • Bahasa Melayu
    • Català
    • Čeština
    • Dansk
    • Deutsch
    • English UK
    • Español
    • Filipino
    • Français
    • Hrvatski
    • Italiano
    • Magyar
    • Nederlands
    • Norsk
    • Polski
    • Português
    • Română
    • Slovenčina
    • Suomi
    • Svenska
    • Tiếng Việt
    • Türkçe
    • Ελληνικά
    • Български език
    • Русский
    • Српски
    • Українська мова
    • עִבְרִית
    • العربية
    • فارسی
    • मराठी
    • हिन्दी
    • বাংলা
    • ગુજરાતી
    • தமிழ்
    • ಕನ್ನಡ
    • ภาษาไทย
    • 한국어
    • 日本語
    • 简体中文
    • 繁體中文
  • Have an account? Log in
    Have an account?
    · Forgot password?

    New to Twitter?
    Sign up
pcwalton's profile
Patrick Walton
Patrick Walton
Patrick Walton
@pcwalton

Tweets

Patrick Walton

@pcwalton

Research engineer at Mozilla

San Francisco, CA
pcwalton.github.io
Joined November 2009

Tweets

  • © 2020 Twitter
  • About
  • Help Center
  • Terms
  • Privacy policy
  • Imprint
  • Cookies
  • Ads info
Dismiss
Previous
Next

Go to a person's profile

Saved searches

  • Remove
  • In this conversation
    Verified accountProtected Tweets @
Suggested users
  • Verified accountProtected Tweets @
  • Verified accountProtected Tweets @

Promote this Tweet

Block

  • Tweet with a location

    You can add location information to your Tweets, such as your city or precise location, from the web and via third-party applications. You always have the option to delete your Tweet location history. Learn more

    Your lists

    Create a new list


    Under 100 characters, optional

    Privacy

    Copy link to Tweet

    Embed this Tweet

    Embed this Video

    Add this Tweet to your website by copying the code below. Learn more

    Add this video to your website by copying the code below. Learn more

    Hmm, there was a problem reaching the server.

    By embedding Twitter content in your website or app, you are agreeing to the Twitter Developer Agreement and Developer Policy.

    Preview

    Why you're seeing this ad

    Log in to Twitter

    · Forgot password?
    Don't have an account? Sign up »

    Sign up for Twitter

    Not on Twitter? Sign up, tune into the things you care about, and get updates as they happen.

    Sign up
    Have an account? Log in »

    Two-way (sending and receiving) short codes:

    Country Code For customers of
    United States 40404 (any)
    Canada 21212 (any)
    United Kingdom 86444 Vodafone, Orange, 3, O2
    Brazil 40404 Nextel, TIM
    Haiti 40404 Digicel, Voila
    Ireland 51210 Vodafone, O2
    India 53000 Bharti Airtel, Videocon, Reliance
    Indonesia 89887 AXIS, 3, Telkomsel, Indosat, XL Axiata
    Italy 4880804 Wind
    3424486444 Vodafone
    » See SMS short codes for other countries

    Confirmation

     

    Welcome home!

    This timeline is where you’ll spend most of your time, getting instant updates about what matters to you.

    Tweets not working for you?

    Hover over the profile pic and click the Following button to unfollow any account.

    Say a lot with a little

    When you see a Tweet you love, tap the heart — it lets the person who wrote it know you shared the love.

    Spread the word

    The fastest way to share someone else’s Tweet with your followers is with a Retweet. Tap the icon to send it instantly.

    Join the conversation

    Add your thoughts about any Tweet with a Reply. Find a topic you’re passionate about, and jump right in.

    Learn the latest

    Get instant insight into what people are talking about now.

    Get more of what you love

    Follow more accounts to get instant updates about topics you care about.

    Find what's happening

    See the latest conversations about any topic instantly.

    Never miss a Moment

    Catch up instantly on the best stories happening as they unfold.

    1. Anthony Ramine‏ @nokusu 22 Nov 2019
      • Report Tweet
      • Report NetzDG Violation
      Replying to @pcwalton @rikarends @chadaustin

      I thought there won’t be any cross-process texture sharing on macOS anymore?

      1 reply 0 retweets 0 likes
    2. Alan Jeffrey‏ @asajeffrey 22 Nov 2019
      • Report Tweet
      • Report NetzDG Violation
      Replying to @nokusu @pcwalton and

      It uses surfaces as a way to safely share send texture data between threads. Happier?

      1 reply 0 retweets 0 likes
    3. Anthony Ramine‏ @nokusu 22 Nov 2019
      • Report Tweet
      • Report NetzDG Violation
      Replying to @asajeffrey @pcwalton and

      Oh cross threads! Ok that makes more sense.

      1 reply 0 retweets 0 likes
    4. Alan Jeffrey‏ @asajeffrey 22 Nov 2019
      • Report Tweet
      • Report NetzDG Violation
      Replying to @nokusu @pcwalton and

      Servo makes sure that any threads using the GPU are all in the same process. There might be clever way to get surfaces sent between processes, but we're not using it.

      1 reply 0 retweets 0 likes
    5. Anthony Ramine‏ @nokusu 22 Nov 2019
      • Report Tweet
      • Report NetzDG Violation
      Replying to @asajeffrey @pcwalton and

      There are definitely support for IPC surfaces in the serde serialisation stuff, and we mark surfaces on macOS global for that very purpose. Glad to know we don’t actually use that though.

      1 reply 0 retweets 0 likes
    6. Patrick Walton‏ @pcwalton 22 Nov 2019
      • Report Tweet
      • Report NetzDG Violation
      Replying to @nokusu @asajeffrey and

      There are ways to send surfaces cross-process on each OS. In fact, they're basically the same ways surfman sends them across threads. They require some extra APIs surfman doesn't use yet, though. e.g. on macOS you can convert an IOSurface to a Mach port and back.

      2 replies 0 retweets 0 likes
    7. Patrick Walton‏ @pcwalton 22 Nov 2019
      • Report Tweet
      • Report NetzDG Violation
      Replying to @pcwalton @nokusu and

      You don't have to mark a surface global to use these APIs. I don't bother to wrap those APIs at the moment because we shouldn't be sending surfaces cross-process in general. Any process that can access the GPU should basically be considered trusted.

      1 reply 0 retweets 0 likes
    8. Anthony Ramine‏ @nokusu 22 Nov 2019
      • Report Tweet
      • Report NetzDG Violation
      Replying to @pcwalton @asajeffrey and

      Why does Firefox do that then? I've searched for a long time, and AFAICT that's the only way to share surfaces.

      1 reply 0 retweets 0 likes
    9. Patrick Walton‏ @pcwalton 22 Nov 2019
      • Report Tweet
      • Report NetzDG Violation
      Replying to @nokusu @asajeffrey and

      Because the content process can access the GPU in Firefox. This is a large security deficiency in Firefox relative to Chrome :( They're actively fixing it.

      1 reply 0 retweets 2 likes
    10. Anthony Ramine‏ @nokusu 22 Nov 2019
      • Report Tweet
      • Report NetzDG Violation
      Replying to @pcwalton @asajeffrey and

      Oh, I misunderstood things about the Mach ports. https://bugs.chromium.org/p/chromium/issues/detail?id=323304 …

      1 reply 0 retweets 0 likes
      Patrick Walton‏ @pcwalton 22 Nov 2019
      • Report Tweet
      • Report NetzDG Violation
      Replying to @nokusu @asajeffrey and

      In general, it's too risky to put content JS and GPU access in the same process. GPU drivers are just too buggy, especially on macOS. Even an out-of-bounds VRAM read could be used to effectively take screenshots of the user's desktop.

      10:06 AM - 22 Nov 2019
      • 1 Retweet
      • 3 Likes
      • Alan Jeffrey Jed Davis 🏳️‍🌈 Anthony Ramine
      2 replies 1 retweet 3 likes
        1. New conversation
        2. Anthony Ramine‏ @nokusu 22 Nov 2019
          • Report Tweet
          • Report NetzDG Violation
          Replying to @pcwalton @asajeffrey and

          Reading the Chromium ticket, we also use globally registered Mach ports in ipc-channel, don't we? Is this something we would like to get rid of at some point?

          1 reply 0 retweets 0 likes
        3. Patrick Walton‏ @pcwalton 22 Nov 2019
          • Report Tweet
          • Report NetzDG Violation
          Replying to @nokusu @asajeffrey and

          Do we? It's been so long since I really dove into ipc-channel. Manish, Nika, and I have been talking about switching ipc-channel to be a layer on top of Chromium's Mojo IPC at some point, which would let us stop having to maintain that stuff.

          2 replies 0 retweets 0 likes
        4. 2 more replies
        1. New conversation
        2. Ted Mielczarek‏ @TedMielczarek 22 Nov 2019
          • Report Tweet
          • Report NetzDG Violation
          Replying to @pcwalton @nokusu and

          What's the safer alternative? Just using IPC to transfer desired draw calls/layer state/whatever? (Presumably as long as you have shared memory to transfer textures it'd be OK?)

          1 reply 0 retweets 0 likes
        3. Patrick Walton‏ @pcwalton 22 Nov 2019
          • Report Tweet
          • Report NetzDG Violation
          Replying to @TedMielczarek @nokusu and

          Yeah, proxy high-level graphics commands over to another trusted process, using memory-safe IPC code.

          1 reply 0 retweets 3 likes
        4. 12 more replies

      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.

        Promoted Tweet

        false

        • © 2020 Twitter
        • About
        • Help Center
        • Terms
        • Privacy policy
        • Imprint
        • Cookies
        • Ads info