Backed out changeset 82cd657ce425 (bug 1906260) for causing mochitest failures @ test_interactive_widget.html & pup wd test failures CLOSED TREE

docs/contributing/debugging/debugging_firefox_with_lldb.rst

@@ -65,7 +65,7 @@ followed by the command line you'd like to run, like this:
 
 .. code:: bash
 
-   $ lldb -- obj-ff-dbg/dist/Nightly.app/Contents/MacOS/firefox -profile /path/to/profile
+   $ lldb -- obj-ff-dbg/dist/Nightly.app/Contents/MacOS/firefox -no-remote -profile /path/to/profile
 
 Then set breakpoints you need and start the process:
 

docs/contributing/debugging/debugging_on_macos.rst

@@ -148,7 +148,8 @@ These steps were last updated for Xcode 15:
    debugging purposes" below. Select the "Arguments" tab in the scheme
    editor, and click the '+' below the "Arguments passed on launch"
    field. Add "-P *profilename*", where *profilename* is the name of a
-   profile you created previously.
+   profile you created previously. Repeat that to also add the argument
+   "-no-remote".
 #. Also in the "Arguments" panel, you may want to add an environment
    variable MOZ_DEBUG_CHILD_PROCESS set to the value 1 to help with
    debugging e10s.

docs/contributing/debugging/debugging_on_windows.rst

@@ -262,7 +262,18 @@ Running two instances of Mozilla simultaneously
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 
 You can run two instances of Mozilla (e.g. debug and optimized)
-simultaneously by specifying the profile to use with the ``-P profile_name``
+simultaneously by setting the environment variable ``MOZ_NO_REMOTE``:
+
+.. code::
+
+   set MOZ_NO_REMOTE=1
+
+Or, starting with Firefox 2 and other Gecko 1.8.1-based applications,
+you can use the ``-no-remote`` command-line switch instead (implemented
+in
+`bug 325509 <https://bugzilla.mozilla.org/show_bug.cgi?id=325509>`__).
+
+You can also specify the profile to use with the ``-P profile_name``
 command-line argument.
 
 Debugging JavaScript