From 1bb524d12bb9a14cd8f21a236aa2fac0aab8f1b3 Mon Sep 17 00:00:00 2001
From: Raymond Hill <rhill@raymondhill.net>
Date: Sat, 14 Dec 2019 11:14:00 -0500
Subject: [PATCH] Still try to load filter lists after fatal error at launch

Related discussion:
- https://github.com/uBlockOrigin/uBlock-issues/issues/817#issuecomment-565730122

In case of a fatal error at launch, the loading of filter lists
could be skipped. With this commit uBO will still try to load
the filter lists, at least the default ones if no valid selfie
is present.
---
 src/js/start.js | 7 +++++++
 1 file changed, 7 insertions(+)

diff --git a/src/js/start.js b/src/js/start.js
index 7cd573f5c..6b9f32434 100644
--- a/src/js/start.js
+++ b/src/js/start.js
@@ -286,7 +286,14 @@ try {
             log.info(`PSL ready ${Date.now()-vAPI.T0} ms after launch`);
         }),
     ]);
+} catch (ex) {
+    console.trace(ex);
+}
 
+// https://github.com/uBlockOrigin/uBlock-issues/issues/817#issuecomment-565730122
+//   Still try to load filter lists regardless of whether a serious error
+//   occurred in the previous initialization steps.
+try {
     const selfieIsValid = await µb.selfieManager.load();
     if ( selfieIsValid === true ) {
         log.info(`Selfie ready ${Date.now()-vAPI.T0} ms after launch`);