[2026-09-08] eagle: work/projects/cpm-web-extension-breakage-findings.md

This commit is contained in:
Alexey Martemyanov
2026-09-08 20:32:28 +06:00
parent 635ac99393
commit af02d80544
@@ -458,10 +458,11 @@ This state ends only when something calls `unloadBackgroundWebView` or unloads/r
- Background WebContent-process termination callback - Background WebContent-process termination callback
- Background navigation failure callback - Background navigation failure callback
- Normal background eviction, if its timer is able to reach the unload path
- Explicit extension-context unload/reload - Explicit extension-context unload/reload
- App process restart - 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: 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. - 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.