Skip to content
Snippets Groups Projects
  1. Jan 05, 2025
    • Kershaw Chang's avatar
      Bug 1907726 - Make sure WebTransportSessionProxy::NotifyDatagramReceived is... · 63f27157
      Kershaw Chang authored and ma1's avatar ma1 committed
      Bug 1907726 - Make sure WebTransportSessionProxy::NotifyDatagramReceived is called after OnStopRequest,  a=RyanVM
      
      The crash occurs because WebTransportSessionProxy::OnDatagramReceivedInternal is called before WebTransportSessionProxy::OnStopRequest.
      When this happens, WebTransportSessionProxy::mTarget is the main thread, so a task is dispatched to the main thread. This causes WebTransportSessionProxy::NotifyDatagramReceived to be called on the main thread.
      
      If WebTransportSessionProxy::NotifyDatagramReceived is invoked while WebTransportSessionProxy::mStopRequestCalled is true, it can lead to OnDatagramReceived being called on the main thread (instead of the socket thread), resulting in a crash.
      
      Original Revision: https://phabricator.services.mozilla.com/D220013
      
      Differential Revision: https://phabricator.services.mozilla.com/D221661
      Verified
      63f27157
  2. May 22, 2023
  3. May 06, 2023
  4. May 05, 2023
  5. May 04, 2023
  6. Apr 27, 2023
  7. Mar 31, 2023
  8. Mar 30, 2023
  9. Mar 28, 2023
  10. Mar 27, 2023
  11. Mar 15, 2023
  12. Mar 07, 2023
  13. Mar 03, 2023
  14. Mar 02, 2023
  15. Feb 24, 2023
  16. Feb 23, 2023
    • Randell Jesup's avatar
      Bug 1817129: Ensure OnSessionClosed is called in error paths for AsyncConnect... · 2dd6eaa4
      Randell Jesup authored
      Bug 1817129: Ensure OnSessionClosed is called in error paths for AsyncConnect r=kershaw,necko-reviewers
      
      WebTransportSessionProxy::AsyncConnect needs to ensure the caller gets the
      normal callback from AsyncConnect, or require that they not wait for it on
      an error return from AsyncConnect.   Also, several error paths didn't clear
      the listener and didn't change the state to 'DONE'.
      
      Differential Revision: https://phabricator.services.mozilla.com/D170028
      2dd6eaa4
    • Iulian Moraru's avatar
      Backed out 14 changesets (bug 1815997, bug 1811624, bug 1814122, bug 1818074,... · e79cbd00
      Iulian Moraru authored
      Backed out 14 changesets (bug 1815997, bug 1811624, bug 1814122, bug 1818074, bug 1815993, bug 1811958, bug 1814113, bug 1790678, bug 1817130, bug 1817129, bug 1814750, bug 1817521) for causing bp-hybrid build bustages related to WebTransport. CLOSED TREE
      
      Backed out changeset 8cfdfa663856 (bug 1790678)
      Backed out changeset 44f5c3b41dac (bug 1818074)
      Backed out changeset debbb57f5328 (bug 1817130)
      Backed out changeset 85dac52e3e4c (bug 1817521)
      Backed out changeset ddb0ea4cdda2 (bug 1817129)
      Backed out changeset 799ad4a11f33 (bug 1815993)
      Backed out changeset fc263dcd3c5e (bug 1790678)
      Backed out changeset 331d1209db0d (bug 1814113)
      Backed out changeset 738d3cb6d163 (bug 1814122)
      Backed out changeset 4c743c9e706a (bug 1814750)
      Backed out changeset e7e0a6849e43 (bug 1811624)
      Backed out changeset c8a708ab94c5 (bug 1811958)
      Backed out changeset 62a3991715fb (bug 1814113)
      Backed out changeset 85d446d9d20c (bug 1815997)
      e79cbd00
    • Randell Jesup's avatar
      Bug 1817129: Ensure OnSessionClosed is called in error paths for AsyncConnect... · e5b96511
      Randell Jesup authored
      Bug 1817129: Ensure OnSessionClosed is called in error paths for AsyncConnect r=kershaw,necko-reviewers
      
      WebTransportSessionProxy::AsyncConnect needs to ensure the caller gets the
      normal callback from AsyncConnect, or require that they not wait for it on
      an error return from AsyncConnect.   Also, several error paths didn't clear
      the listener and didn't change the state to 'DONE'.
      
      Differential Revision: https://phabricator.services.mozilla.com/D170028
      e5b96511
  17. Feb 13, 2023
  18. Feb 10, 2023
  19. Feb 02, 2023
  20. Jan 16, 2023
    • Nika Layzell's avatar
      Bug 1809753 - Part 3: Replace all callers of GetCurrentEventTarget with... · 852d02ec
      Nika Layzell authored
      Bug 1809753 - Part 3: Replace all callers of GetCurrentEventTarget with GetCurrentSerialEventTarget, r=mccr8,necko-reviewers,valentin
      
      This only changes the behaviour when called with a TaskQueue or other type
      using SerialEventTargetGuard on the stack. They are being switched over as the
      existing GetCurrentEventTarget method is being removed, as it is somewhat
      confusing, and poorly documented.
      
      Callers which need to get the current thread even when on a threadpool or
      behind a TaskQueue were switched to GetCurrentEventTarget in the previous part.
      
      Differential Revision: https://phabricator.services.mozilla.com/D166607
      852d02ec
  21. Jan 17, 2023
    • Sandor Molnar's avatar
      Backed out 6 changesets (bug 1809752, bug 1809753) for causing perma failures... · 41b78439
      Sandor Molnar authored
      Backed out 6 changesets (bug 1809752, bug 1809753) for causing perma failures in browser/components/firefoxview/tests/browser/browser_feature_callout_position.js
      
      Backed out changeset ea05784d74c4 (bug 1809753)
      Backed out changeset 7c9b20eebcc8 (bug 1809753)
      Backed out changeset d0267ac2256d (bug 1809753)
      Backed out changeset aa9f2971bd6f (bug 1809753)
      Backed out changeset f0d9fcfaa6f8 (bug 1809752)
      Backed out changeset 6d58c799cffe (bug 1809752)
      41b78439
  22. Jan 16, 2023
    • Nika Layzell's avatar
      Bug 1809753 - Part 3: Replace all callers of GetCurrentEventTarget with... · 8d118308
      Nika Layzell authored
      Bug 1809753 - Part 3: Replace all callers of GetCurrentEventTarget with GetCurrentSerialEventTarget, r=mccr8,necko-reviewers,valentin
      
      This only changes the behaviour when called with a TaskQueue or other type
      using SerialEventTargetGuard on the stack. They are being switched over as the
      existing GetCurrentEventTarget method is being removed, as it is somewhat
      confusing, and poorly documented.
      
      Callers which need to get the current thread even when on a threadpool or
      behind a TaskQueue were switched to GetCurrentEventTarget in the previous part.
      
      Differential Revision: https://phabricator.services.mozilla.com/D166607
      8d118308
  23. Jan 12, 2023
  24. Jan 11, 2023
  25. Jan 10, 2023
  26. Jan 03, 2023
Loading