Bug: breadcrumb-webview2-init-fails-resource-not-in-correct-state

[drmoisan]

• Work Mode: full-bug

Summary

The breadcrumb CoreWebView2 initialization fails intermittently with HRESULT 0x8007139F ("The group or resource is not in the correct state to perform the requested operation"), logged by both WebView2BreadcrumbHost and EfcFormController. The failure is logged and swallowed; the session continues with a breadcrumb host that never initialized, and a later BreadcrumbUiDispatcher dispatch fails in the same session. Because the #677 keyboard-lock mechanism is WebView2 focus retention, a half-initialized WebView2 is a plausible contributor to the sporadic keyboard lock, but that link is unconfirmed.

Environment

• OS/version: Windows 11 Pro 10.0.26200
• Python version: n/a (C# / .NET Framework 4.8 VSTO add-in)
• Command/flags used: QuickFiler launched from the ribbon (High Confidence button); add-in loaded from TaskMaster\bin\Debug built 2026-09-06 08:51 from 7c8ac9ae
• Data source or fixture: live Outlook Inbox view

Steps to Reproduce

1. Launch QuickFiler from the ribbon several times in one Outlook session.
2. Inspect TaskMaster\bin\Debug\logs\debug_<date>.log for Breadcrumb CoreWebView2 initialization failed.
3. Observe that the failure occurs on some launches (2 of 6 today: 08:55:22 and 10:06:51) and not others.

Not reproducible on demand.

Expected Behavior

WebView2 initialization either succeeds, or fails with a clear surfaced error and a defined fallback state that cannot retain keyboard focus. A failed initialization should be retried or the host disposed, not left half-constructed.

Actual Behavior

Two ERROR lines per occurrence (WebView2BreadcrumbHost - Breadcrumb CoreWebView2 initialization failed: ... (HRESULT: 0x8007139F) and EfcFormController - Breadcrumb WebView2 initialization failed: ...), then normal operation continues. A BreadcrumbUiDispatcher - Breadcrumb UI dispatch failed. error followed at 09:01:56 in the same session.

Logs / Screenshots

• Attached minimal logs or screenshot
• Snippet (debug_2026-09-06.log):

2026-09-06 08:55:22,227 [VSTA_Main] ERROR QuickFiler.Viewers.WebView2BreadcrumbHost - Breadcrumb CoreWebView2 initialization failed: ... (HRESULT: 0x8007139F)
2026-09-06 08:55:22,286 [VSTA_Main] ERROR QuickFiler.Controllers.EfcFormController - Breadcrumb WebView2 initialization failed: ... (HRESULT: 0x8007139F)
2026-09-06 09:01:56,237 [VSTA_Main] ERROR QuickFiler.Viewers.BreadcrumbUiDispatcher - Breadcrumb UI dispatch failed.
2026-09-06 10:06:51,594 [VSTA_Main] ERROR QuickFiler.Viewers.WebView2BreadcrumbHost - Breadcrumb CoreWebView2 initialization failed: ... (HRESULT: 0x8007139F)
2026-09-06 10:06:51,661 [VSTA_Main] ERROR QuickFiler.Controllers.EfcFormController - Breadcrumb WebView2 initialization failed: ... (HRESULT: 0x8007139F)

Impact / Severity

• Blocker
• High
• Medium
• Low

Medium: the breadcrumb folder selector is unavailable on affected launches, and the half-initialized control is a candidate contributor to the sporadic Outlook keyboard lock tracked under the sibling QuickFiler Cancel-teardown issue filed the same day.

Source

From: docs/features/potential/2026-09-06-breadcrumb-webview2-init-fails-resource-not-in-correct-state.md

[drmoisan]

Update 2026-09-06: reproduces on every Efc open via pop-out and Sort Email; severity raised to High

Two user-visible symptoms reported today are this failure:

1. Pop-out from a QfcItem to an EfcItem shows an empty folder list. No suggestions, no banners, and typing a search string does nothing.
2. Ribbon -> Sort Email opens an EfcViewer whose "Matched Folders:" section has no entries. The label is a static WinForms label above the breadcrumb WebView2, which is why it survives while the list is blank.

Log evidence

TaskMaster\bin\Debug\logs\debug_2026-09-06.log records the paired WebView2BreadcrumbHost / EfcFormController initialization failure with HRESULT 0x8007139F on every Efc open in the session: ten pop-out opens between 17:39:00 and 17:41:42, three at 19:04-19:06, and the Sort Email open at 19:56:36 (the SortEmail_Click stack at 19:56:36,171 is followed by the failure at 19:56:37,940). Today the failure is deterministic on the Efc entry points, not intermittent as originally recorded.

2026-09-06 19:56:37,940 [VSTA_Main] ERROR QuickFiler.Viewers.WebView2BreadcrumbHost - Breadcrumb CoreWebView2 initialization failed: The group or resource is not in the correct state to perform the requested operation. (Exception from HRESULT: 0x8007139F)
2026-09-06 19:56:38,004 [VSTA_Main] ERROR QuickFiler.Controllers.EfcFormController - Breadcrumb WebView2 initialization failed: The group or resource is not in the correct state to perform the requested operation. (Exception from HRESULT: 0x8007139F)

Why the list is blank rather than degraded

• BreadcrumbBridgeRouter.DeliverDocument (QuickFiler\Controllers\BreadcrumbBridgeRouter.Selection.cs:168-180) stashes the rendered document in _pendingDocument when _host.IsCoreInitialized is false. WebView2BreadcrumbHost (:330-342) returns on !e.IsSuccess without ever raising CoreInitialized, so the pending document is never navigated. There is no fallback rendering and no retry.
• EfcFormController.InitializeBreadcrumbHostAsync (:1071-1081) and PopulateFolderCombobox (:1250-1271) are fire-and-forget tasks with total catch blocks, so the failure is log-only.
• EfcFormController.BindBreadcrumbRowsAsync (:1115-1118) reads _globals.Ol.ArchiveRootPath unguarded; TryGetArchiveRoot (EfcDataModel.cs:280-297) is not used on the bind path.

Additional latent defect on the pop-out path

QfcCollectionController.PopOutControlGroup (QuickFiler\Controllers\QfcCollectionController.cs:710-735) hands only the raw MailItem and _globals to new EfcHomeController(...) via the synchronous constructor, so the Efc view rebuilds prediction from scratch with an unloaded MailItemHelper (EfcDataModel.cs:48-81 vs CreateAsync :89-142). The in-QuickFiler carry pattern from #678 (QfcItemController.FolderHandling.cs:68-83, _carriedFolderHandler) is not applied to the pop-out. EfcViewerQueue.BuildQueue has no production call site, so EfcViewer is always constructed inline on the calling thread and captures SynchronizationContext.Current as-is (EfcViewer.cs:23-30); if the pop-out continuation lands off the UI thread, UiThread.SynchronizationContextAwaiter throws on the null context (UiThread.cs:91-98) inside the same swallowed tasks.

Additional acceptance criteria (settled with the maintainer 2026-09-06)

• AC-U1: A failed CoreWebView2 initialization is retried, and on final failure the Efc view shows a visible error state in the folder area instead of a blank list.
• AC-U2: _pendingDocument is never silently dropped: it is delivered when initialization later succeeds or an error is surfaced.
• AC-U3: The pop-out path carries the already-initialized folder predictor and loaded MailItemHelper from the QfcItem, following the Bug: quickfiler-carry-folder-predictor-to-item-controller #678 carry pattern, and constructs the EfcViewer on the UI thread.
• AC-U4: PopulateFolderCombobox and InitializeBreadcrumbHostAsync report failures through TryReportBoundaryFault to the user, not log-only.
• AC-U5: Manual verification on both entry points: pop-out from QuickFiler and ribbon Sort Email each show suggestion rows and respond to typed search.

Severity: raised from Medium to High. Both Efc entry points are unusable for folder selection in the affected sessions.