Bug 1517636: Follow-up - fix eslint error; r=bustage
authorAaron Klotz <aklotz@mozilla.com>
Tue, 15 Jan 2019 17:39:18 -0700
changeset 514032 1f0d9b94c057fd473932d359d7e04289c6d4016e
parent 514031 447687e20dac74b338c8955ebb2d35ddfebd1fc7
child 514033 847d1877fedaf7f30271b6a217138b80d0e7cbf2
push id1953
push userffxbld-merge
push dateMon, 11 Mar 2019 12:10:20 +0000
treeherdermozilla-release@9c35dcbaa899 [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;