tor-browser

commit 3709f413659b907bc94c8ed623015d2a245ed61a
parent c9c85c0f361181e85d7a3556be4afdd2d8d131c4
Author: Ted Campbell <tcampbell@mozilla.com>
Date:   Wed,  7 Jan 2026 06:25:57 +0000

Bug 2005839 - Part 2: Remove strictMode guard when starting core.engine r=android-reviewers,jonalmeida

The strict-mode allowViolation code has itself touched components.core.engine in order
to access profiler markers so in practice _that_ was triggering engine warmup. Since
that wasn't giving a violation in recent years, let's remove the allowViolation call.

Differential Revision: https://phabricator.services.mozilla.com/D276812

Diffstat:
M
mobile/android/fenix/app/src/androidTest/java/org/mozilla/fenix/perf/StartupExcessiveResourceUseTest.kt
 | 
2
+-
M
mobile/android/fenix/app/src/main/java/org/mozilla/fenix/FenixApplication.kt
 | 
4
+---

2 files changed, 2 insertions(+), 4 deletions(-)
diff --git a/mobile/android/fenix/app/src/androidTest/java/org/mozilla/fenix/perf/StartupExcessiveResourceUseTest.kt b/mobile/android/fenix/app/src/androidTest/java/org/mozilla/fenix/perf/StartupExcessiveResourceUseTest.kt
@@ -33,7 +33,7 @@ import org.mozilla.fenix.helpers.HomeActivityTestRule
  *
  * Say no to main thread IO! 🙅
  */
-private const val EXPECTED_SUPPRESSION_COUNT = 12
+private const val EXPECTED_SUPPRESSION_COUNT = 11
 
 /**
  * The number of times we call the `runBlocking` coroutine method on the main thread during this
diff --git a/mobile/android/fenix/app/src/main/java/org/mozilla/fenix/FenixApplication.kt b/mobile/android/fenix/app/src/main/java/org/mozilla/fenix/FenixApplication.kt
@@ -230,9 +230,7 @@ open class FenixApplication : LocaleAwareApplication(), Provider {
 
         run {
             // Make sure the engine is initialized and ready to use.
-            components.strictMode.allowViolation(StrictMode::allowThreadDiskReads) {
-                components.core.engine.warmUp()
-            }
+            components.core.engine.warmUp()
 
             initializeGlean()