Add early return for disabled feature in DuckChatDeleter

cursoragent · cursoragent · commit e4efef8e4901 · 2026-03-09T14:12:31.000Z
When duckAiDataClearingFeature is disabled (the default), deleteChat() now
returns false immediately instead of spinning up a WebView, loading pages
for two domains, injecting JS, and waiting for timeouts that will never
complete. This avoids up to ~10 seconds of unnecessary suspended delay
per tab burn when the feature is disabled.
diff --git a/duckchat/duckchat-impl/src/main/java/com/duckduckgo/duckchat/impl/clearing/RealDuckChatDeleter.kt b/duckchat/duckchat-impl/src/main/java/com/duckduckgo/duckchat/impl/clearing/RealDuckChatDeleter.kt
@@ -72,6 +72,8 @@ class RealDuckChatDeleter @Inject constructor(
     private var cachedScript: String? = null
 
     override suspend fun deleteChat(chatId: String): Boolean {
+        if (!duckAiDataClearingFeature.self().isEnabled()) return false
+
         return mutex.withLock {
             withContext(dispatchers.main()) {
                 try {
