1. 26 Sep, 2019 6 commits
  2. 22 Sep, 2019 1 commit
  3. 26 Sep, 2019 6 commits
  4. 13 Sep, 2019 1 commit
  5. 26 Sep, 2019 6 commits
  6. 24 Sep, 2019 1 commit
  7. 26 Sep, 2019 2 commits
    • thomasmo's avatar
      Bug 1581855:Part 2 - Present VR output to VR Host r=kip,jrmuizel,sotaro,bryce · ab2f6483
      thomasmo authored
      This change is a continuation of Part 1 (Bug 1570128), where the 2D content rendered by Firefox for Firefox Reality on Desktop is marshalled through VRHost so that it can be presented in a VR environment.
      A new class, FxrOutputHandler, is created to manage creating a sharable texture, sharing it through VRShMem, and updating it when content updates. This class updates content with both WebRender and conventional rendering output.
      This initial iteration of FxrOutputHandler does not have synchronization between reading and writing this shared texture across processes. A subsequent fix (Bug 1581881) is pending, which will reuse WebVR code to manage writing to and reading from a pool of textures.
      This also presents issues with rendering protected media, so an additional class, FxrWindowManager, is created to manage all windows created for Firefox Reality on Desktop so that it can inform whether or not protected media can be presented.
      The automated manual tests in vrhosttest.cpp now show the real shared texture handle rather than a fake value, which shows that marshaling succeeded.
      
      Differential Revision: https://phabricator.services.mozilla.com/D46179
      
      --HG--
      extra : moz-landing-system : lando
      ab2f6483
    • Thomas Wisniewski's avatar
      Bug 1581180 - Fix browser_report_site_issue.js test on Fission r=denschub · 216d51df
      Thomas Wisniewski authored
      Fix browser_report_site_issue.js test on Fission
      
      Differential Revision: https://phabricator.services.mozilla.com/D46420
      
      --HG--
      extra : moz-landing-system : lando
      216d51df
  8. 25 Sep, 2019 1 commit
    • Nathan Froyd's avatar
      Bug 1583964 - make `IsOnCurrentThread` for thread pools constant-time; r=KrisWright · 5a3128b9
      Nathan Froyd authored
      It's fairly common for clients to hold a pointer to some private thread
      and then inquire about `IsOnCurrentThread` in debug checks.  As we
      migrate these private threads into some `nsIEventTarget` implementation
      that might be running on thread pools, we need to ensure that those
      `IsOnCurrentThread` continues to be relatively cheap.  The current
      implementation for thread pools is not particularly efficient.
      
      The inefficiency comes from having to iterate over all the threads in
      the pool.  But there's no need to do this; we can just have each thread
      set a particular thread-local variable to the thread pool it's running
      on, and check the value of that thread-local variable instead.
      
      Differential Revision: https://phabricator.services.mozilla.com/D47139
      
      --HG--
      extra : moz-landing-system : lando
      5a3128b9
  9. 26 Sep, 2019 1 commit
  10. 23 Sep, 2019 1 commit
  11. 26 Sep, 2019 1 commit
  12. 23 Sep, 2019 1 commit
  13. 26 Sep, 2019 1 commit
  14. 23 Sep, 2019 3 commits
  15. 26 Sep, 2019 8 commits