Race-condition loading add-ons in Orfox
It seems like there is a race condition when loading add-on at first-install/run. We noticed https-everywhere sometimes is not installed after freshly installing Orfox.
Is this a regressions from 52.2.x?
When https-everywhere is not installed during the first-run after installing, the .xpi is copied into <profile_dir>/extensions/staged/ but it remains there. Restarting the app does not cause it to be installed.
However, we found Orfox does install the https-everywhere extension if we disable the NoScriptAnywhere (NSA) extensions and then restart the app.
But it seems NSA is not the cause of this problem because after reinstalling the Orfox app (and confirming https-everywhere was not installed), we found https-everywhere is installed after toggling extensions.logging.enabled and then restarting the app. Maybe the extra logging slows the app enough.