From af02d80544d1a9e65ad6506fe40bf2fa17aace0c Mon Sep 17 00:00:00 2001 From: Alexey Martemyanov Date: Tue, 8 Sep 2026 20:32:28 +0600 Subject: [PATCH] [2026-09-08] eagle: work/projects/cpm-web-extension-breakage-findings.md --- work/projects/cpm-web-extension-breakage-findings.md | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/work/projects/cpm-web-extension-breakage-findings.md b/work/projects/cpm-web-extension-breakage-findings.md index 03e51f28..8beb69f6 100644 --- a/work/projects/cpm-web-extension-breakage-findings.md +++ b/work/projects/cpm-web-extension-breakage-findings.md @@ -458,10 +458,11 @@ This state ends only when something calls `unloadBackgroundWebView` or unloads/r - Background WebContent-process termination callback - Background navigation failure callback -- Normal background eviction, if its timer is able to reach the unload path - Explicit extension-context unload/reload - App process restart +The ordinary 30-second nonpersistent-background eviction does not recover the failed-first-load sequence. The wake-up call tries to schedule eviction before the background view is created, so it returns without creating a timer; the failure path never schedules the timer afterward. + Opening an ordinary new browser window does not itself unload or reload the shared extension context. Therefore: - If a new window works while the original remains broken, this exact all-tabs freeze is not the state currently being observed; the failure is more likely tab/process routing.