What happened?
This issue is a regression (last working version: 147.0.3912.98).
Description:
After updating to WebView2 Runtime 148.0.3967.83, the crash when opening edge://history/all is still reproducible. The last version where the history page worked correctly was 147.0.3912.98.
Steps to Reproduce:
Launch a WebView2 control with Runtime 148.0.3967.83.
Navigate to edge://history/all.
Observe the behavior described below.
Actual Behavior:
The history page is displayed for several seconds, but the history items are not interactive. Shortly after, the application is redirected to an error page showing:
RESULT_CODE_KILLED_BAD_MESSAGE
Questions:
When can we expect a fix for this issue?
Are there any alternative ways to access or view browsing history in WebView2 while this bug remains unresolved?
Environment:
WebView2 Runtime: 148.0.3967.83
Last working version: 147.0.3912.98
OS: [Windows 11]
App type: [Win32/WPF/WinUI, etc.]
Additional context:
This issue has been present since version later 147.0.3912.98 and persists in the latest runtime.
ProcessFailed logs show FailureReason = KilledBadMessage.
Importance
Moderate. My app's user experience is affected, but still usable.
Runtime Channel
Stable release (WebView2 Runtime)
Runtime Version
No response
SDK Version
No response
Framework
----Please select----
Operating System
Windows 11
OS Version
No response
Repro steps
The page should open normally and allow interaction with history items
Repros in Edge Browser
No, issue does not reproduce in the corresponding Edge version
Regression
WebView2 Runtime: 148.0.3967.83
Last working version (if regression)
WebView2 Runtime: 147.0.3912.98
What happened?
This issue is a regression (last working version: 147.0.3912.98).
Description:
After updating to WebView2 Runtime 148.0.3967.83, the crash when opening edge://history/all is still reproducible. The last version where the history page worked correctly was 147.0.3912.98.
Steps to Reproduce:
Launch a WebView2 control with Runtime 148.0.3967.83.
Navigate to edge://history/all.
Observe the behavior described below.
Actual Behavior:
The history page is displayed for several seconds, but the history items are not interactive. Shortly after, the application is redirected to an error page showing:
RESULT_CODE_KILLED_BAD_MESSAGE
Questions:
When can we expect a fix for this issue?
Are there any alternative ways to access or view browsing history in WebView2 while this bug remains unresolved?
Environment:
WebView2 Runtime: 148.0.3967.83
Last working version: 147.0.3912.98
OS: [Windows 11]
App type: [Win32/WPF/WinUI, etc.]
Additional context:
This issue has been present since version later 147.0.3912.98 and persists in the latest runtime.
ProcessFailed logs show FailureReason = KilledBadMessage.
Importance
Moderate. My app's user experience is affected, but still usable.
Runtime Channel
Stable release (WebView2 Runtime)
Runtime Version
No response
SDK Version
No response
Framework
----Please select----
Operating System
Windows 11
OS Version
No response
Repro steps
The page should open normally and allow interaction with history items
Repros in Edge Browser
No, issue does not reproduce in the corresponding Edge version
Regression
WebView2 Runtime: 148.0.3967.83
Last working version (if regression)
WebView2 Runtime: 147.0.3912.98