Original Revision: https://phabricator.services.mozilla.com/D205447

Differential Revision: https://phabricator.services.mozilla.com/D205452

Original Revision: https://phabricator.services.mozilla.com/D204130

Differential Revision: https://phabricator.services.mozilla.com/D205340

Differential Revision: https://phabricator.services.mozilla.com/D204546

Differential Revision: https://phabricator.services.mozilla.com/D205325

No bug - Tagging f65068dc82bf6051f520551ba5497a5985877d47 with FIREFOX_115_9_1esr_RELEASE a=release CLOSED TREE DONTBUILD

No bug - Tagging f65068dc82bf6051f520551ba5497a5985877d47 with FIREFOX_115_9_1esr_BUILD1 a=release CLOSED TREE DONTBUILD

Bug 1886852 - Avoid registering unnecessary MessageManager listeners when SHIP is enabled, r=smaug, a=dsmith

Differential Revision: https://phabricator.services.mozilla.com/D205377

No bug - Tagging 423e963b3d9b923e3c7fae8eae2f626f02c15cf2 with FIREFOX_115_9_0esr_RELEASE a=release CLOSED TREE DONTBUILD

This removes all the memory allocations which we were doing while writing a
minidump of the crashed process from within the process itself. Under these
conditions all threads are stopped save for the minidump writer; so if another
thread owns a mutex guarding the memory allocator we could deadlock by doing
allocations.

This patch avoids allocating strings entirely and uses Breakpad's alternative
allocator to sidestep the issue where we cannot avoid allocations.

Differential Revision: https://phabricator.services.mozilla.com/D201960

Differential Revision: https://phabricator.services.mozilla.com/D204888

Original Revision: https://phabricator.services.mozilla.com/D202361

Differential Revision: https://phabricator.services.mozilla.com/D202763

No bug - Tagging 423e963b3d9b923e3c7fae8eae2f626f02c15cf2 with FIREFOX_115_9_0esr_BUILD2 a=release CLOSED TREE DONTBUILD

No bug - Tagging f3dd0afed51cb7283d4fa06a0c40286eee657e30 with FIREFOX_115_9_0esr_BUILD1 a=release CLOSED TREE DONTBUILD

Differential Revision: https://phabricator.services.mozilla.com/D204210

The causes of the runnable loop are as follows:
1. In Release we have a special case to make sure OnStart&OnStop are always
   called. We do this by dispatching a runnable that calls DoNotifyListener.
2. DoNotifyListener is called, then the reference to the channel is again
   dropped. But at this point only OnStartRequest was called, and
   ContinueDoNotifyListener was added to mEventQ. That means another
   runnable would be dispatched.

While the loop was broken in the previous patch, we still want to ensure
OnStopRequest is called before the channel is released, so this patch
adds an argument to DoNotifyListener to select whether ContinueDoNotifyListener
should be called synchronously or dispatched to mEventQ.

Original Revision: https://phabricator.services.mozilla.com/D202798

Differential Revision: https://phabricator.services.mozilla.com/D204063

Original Revision: https://phabricator.services.mozilla.com/D202797

Differential Revision: https://phabricator.services.mozilla.com/D204062

Original Revision: https://phabricator.services.mozilla.com/D202796

Differential Revision: https://phabricator.services.mozilla.com/D204061

So as to not change load timing from stylo threads.

Differential Revision: https://phabricator.services.mozilla.com/D203927

Original Revision: https://phabricator.services.mozilla.com/D203103

Differential Revision: https://phabricator.services.mozilla.com/D204101

Bug 1879714 - Update search-telemetry-v2 schema with more functionality and loosen restrictions on component types - r=Standard8, a=dsmith

Differential Revision: https://phabricator.services.mozilla.com/D201313

Bug 1878818 - Change search-telemetry schema to use the same sub-schema syntax as search-config - r=Standard8, a=dsmith

I think the main issue was the use of ids, but also just to keep things a consistent
between the two in case a team member has to learn how to modify both, it might be
better to use the same syntax.

Differential Revision: https://phabricator.services.mozilla.com/D200754

Differential Revision: https://phabricator.services.mozilla.com/D203895

Bug 1804978: Prevent release assert crashes due to a race when opening context menus on macOS. r=mstange, a=dsmith

Differential Revision: https://phabricator.services.mozilla.com/D198700

Original Revision: https://phabricator.services.mozilla.com/D201684

Differential Revision: https://phabricator.services.mozilla.com/D203291

Original Revision: https://phabricator.services.mozilla.com/D202932

Differential Revision: https://phabricator.services.mozilla.com/D203626

This makes the calculation simpler and faster, at a hopefully small
cost in space. Idea by peterv.

This reduced the time to run a microbenchmark locally by around 12%.

Differential Revision: https://phabricator.services.mozilla.com/D202281

That is the only case that uses it. This might save a bit of space
and avoids some useless stores. Idea by peterv.

Differential Revision: https://phabricator.services.mozilla.com/D202344

Differential Revision: https://phabricator.services.mozilla.com/D203411

Differential Revision: https://phabricator.services.mozilla.com/D203050

This patch makes several fundamental changes to the logic we use to inform
the main process whenever the WER runtime exception module intercepts a child
process crash:

* We no longer read the process type or any other data from the child process;
  the process type is passed as the runtime exception module's context
* We no longer read the address of the memory area used to communicate with the
  main process from the child process arguments. Instead we allocate memory
  directly into the main process and store the required information there
* We don't read anything from the main process either, the pointer to the
  function used to notify the main process is now found by looking out its
  dedicated section in the parent process' xul.dll mapping
* We no longer read the OOM crash annotation from a child process, this
  functionality will be restored by making the module use the mozannotation
  crates to fetch all the annotations

Original Revision: https://phabricator.services.mozilla.com/D201589

Differential Revision: https://phabricator.services.mozilla.com/D202916

Original Revision: https://phabricator.services.mozilla.com/D201590

Differential Revision: https://phabricator.services.mozilla.com/D202915

Bug 1872920 - Prevent the crash reporer from restarting Firefox when dealing with WER crashes  a=diannaS

Original Revision: https://phabricator.services.mozilla.com/D199856

Differential Revision: https://phabricator.services.mozilla.com/D202914

Original Revision: https://phabricator.services.mozilla.com/D199353

Differential Revision: https://phabricator.services.mozilla.com/D202913

Original Revision: https://phabricator.services.mozilla.com/D199352

Differential Revision: https://phabricator.services.mozilla.com/D202912