[ci-scan] Recurring: WebViewDoesntCrashWhenLoadingAHeavyPageAndUsingExecutionModeSeparateProcess hangs and force-terminates on macOS in ma [Content truncated due to length]

[github-actions]

Summary

WebViewDoesntCrashWhenLoadingAHeavyPageAndUsingExecutionModeSeparateProcess consistently hangs the test host app (macOS Catalyst) for 12–15 minutes before being force-terminated, blocking the rest of the Controls WebView test category.

Build Information

• Pipeline: maui-pr-uitests (definition 313)
• Build: 1484478
• Build ID: 1484478
• Branch: main
• First seen: 2026-06-26 (build 1483327)
• Occurrences: 2 in last 10 builds (1483327 Jun 26, 1484478 Jun 27)

Affected Legs

• Controls WebView — macOS Catalyst — maui-pr-uitests Job: Controls WebView

Error Message

>>>>> App became unresponsive, force-closing: App.AppState query did not complete — app is likely unresponsive
  Failed WebViewDoesntCrashWhenLoadingAHeavyPageAndUsingExecutionModeSeparateProcess [15 m 8 s]
   The app became unresponsive and was force-terminated: App.AppState query did not complete — app is likely unresponsive
TearDown : The app became unresponsive and was force-terminated: App.AppState query did not complete — app is likely unresponsive
   at UITest.Appium.NUnit.UITestBase.UITestBaseTearDown() in /_/src/TestUtils/src/UITest.NUnit/UITestBase.cs:line 121
   at UITest.Appium.NUnit.UITestBase.TestTearDown() in /_/src/TestUtils/src/UITest.NUnit/UITestBase.cs:line 45

Timeline

• Build 1483327 (Jun 26): Fails with [12 m 53 s] on first attempt, then [3 m 51 s] on retry — both force-terminate.
• Build 1484478 (Jun 27): Fails with [15 m 8 s], force-terminated. Subsequent WebView_SetHtmlSource_VerifyNavigatingEvent, WebView_SetHtmlSource_VerifyNavigatedEvent, and VerifyWebViewWithShadow are cascade failures.
• Build 1486368 (Jun 29): macOS WebView job terminated early (force-quit after CookiesCorrectlyLoadWithMultipleWebViews crashes — tracked in [ci-scan] Recurring: CookiesCorrectlyLoadWithMultipleWebViews fails on iOS/MacCatalyst in maui-pr-uitests #36117), so this test did not execute to completion.

Recommended Action

Investigate the test in src/Controls/tests/TestCases.Shared.Tests/Tests/ for WebViewDoesntCrashWhenLoadingAHeavyPageAndUsingExecutionModeSeparateProcess. The test appears to leave the app in an unresponsive state on macOS Catalyst when loading a heavy page with ExecutionMode.SeparateProcess. Possible causes:

• A deadlock or infinite loop in the WebView SeparateProcess execution path specific to macOS.
• The heavy page triggers a memory/crash condition that Appium cannot recover from within the query timeout.
• Consider adding a timeout-with-screenshot step and increasing Appium query timeout or adding an app-restart guard for this test.

Generated by CI Failure Scanner · 1.5K AIC · ⌖ 23.1 AIC · ⊞ 36.2K · ◷

[PureWeen]

Closing this scanner issue as stale/non-reproducing after exact-test review. WebViewDoesntCrashWhenLoadingAHeavyPageAndUsingExecutionModeSeparateProcess passed without retry across seven complete main UI builds through 1544324, with no matching hang or force-termination signature. No root-cause fix is claimed.