Bug 1517636: Follow-up - fix eslint error; r=bustage
authorAaron Klotz <aklotz@mozilla.com>
Tue, 15 Jan 2019 17:39:18 -0700
changeset 511150 1f0d9b94c057
parent 511149 447687e20dac
child 511151 847d1877feda
push id10547
push userffxbld-merge
push dateMon, 21 Jan 2019 13:03:58 +0000
treeherdermozilla-beta@24ec1916bffe [default view] [failures only]
perfherder[talos] [build metrics] [platform microbench] (compared to previous push)
reviewersbustage
bugs1517636
milestone66.0a1
first release with
nightly linux32
nightly linux64
nightly mac
nightly win32
nightly win64
last release without
nightly linux32
nightly linux64
nightly mac
nightly win32
nightly win64
Bug 1517636: Follow-up - fix eslint error; r=bustage
toolkit/modules/Troubleshoot.jsm
--- a/toolkit/modules/Troubleshoot.jsm
+++ b/toolkit/modules/Troubleshoot.jsm
@@ -194,17 +194,17 @@ var dataProviders = {
                    .useRemoteTabs;
       if (remote) {
         data.numRemoteWindows++;
       }
     }
 
     try {
       data.launcherProcessState = Services.appinfo.launcherProcessState;
-    } catch(e) {}
+    } catch (e) {}
 
     data.remoteAutoStart = Services.appinfo.browserTabsRemoteAutostart;
 
     // Services.ppmm.childCount is a count of how many processes currently
     // exist that might respond to messages sent through the ppmm, including
     // the parent process. So we subtract the parent process with the "- 1",
     // and that’s how many content processes we’re waiting for.
     data.currentContentProcesses = Services.ppmm.childCount - 1;