Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Bug]: ProcessFailed during disposal when a print dialog is open #4317

Open
lezzi opened this issue Jan 23, 2024 · 7 comments
Open

[Bug]: ProcessFailed during disposal when a print dialog is open #4317

lezzi opened this issue Jan 23, 2024 · 7 comments
Assignees
Labels
bug Something isn't working tracked We are tracking this work internally.

Comments

@lezzi
Copy link

lezzi commented Jan 23, 2024

What happened?

When a print dialog is open and a WebView2 instance is disposed, the ProcessFailed event is raised, and all web views crash.

Importance

Moderate. My app's user experience is affected, but still usable.

Runtime Channel

Stable release (WebView2 Runtime)

Runtime Version

120.0.2210.91, 120.0.2210.144

SDK Version

1.0.1722.45, 1.0.2164.0

Framework

WPF

Operating System

Windows 11

OS Version

10.0.22621

Repro steps

  1. Clone and run the WebView2WpfBrowser.
  2. Using the top menu, click on Window -> New Window to create a 2nd window.
  3. Navigate to the https://output.jsbin.com/xizowusota/ and click on the "Print button".
  4. Wait for the print dialog to appear and fully load.
  5. Using the top menu, click on the Window -> New Window.
  6. Observe the WebView2 process crashing.

webview2_crash_print

Repros in Edge Browser

No

Regression

No, this never worked

Last working version (if regression)

No response

AB#48635651

@lezzi lezzi added the bug Something isn't working label Jan 23, 2024
Copy link

Hi, @lezzi!

It seems that your issue contains the word "crash". If you have not already, could you attach a crash dump as a comment?

WV2 crash dumps are located in a subfolder of the app's user data folder (UDF): <UDF>\EBWebView\Crashpad\reports\. By default, the user data folder is created in the app's folder with a name like <App Exe Name>.exe.WebView2. Refer to Crash Diagnostics for more information.

Thank you for your cooperation!

2 similar comments
Copy link

Hi, @lezzi!

It seems that your issue contains the word "crash". If you have not already, could you attach a crash dump as a comment?

WV2 crash dumps are located in a subfolder of the app's user data folder (UDF): <UDF>\EBWebView\Crashpad\reports\. By default, the user data folder is created in the app's folder with a name like <App Exe Name>.exe.WebView2. Refer to Crash Diagnostics for more information.

Thank you for your cooperation!

Copy link

Hi, @lezzi!

It seems that your issue contains the word "crash". If you have not already, could you attach a crash dump as a comment?

WV2 crash dumps are located in a subfolder of the app's user data folder (UDF): <UDF>\EBWebView\Crashpad\reports\. By default, the user data folder is created in the app's folder with a name like <App Exe Name>.exe.WebView2. Refer to Crash Diagnostics for more information.

Thank you for your cooperation!

@lezzi
Copy link
Author

lezzi commented Jan 23, 2024

@monica-ch monica-ch added the tracked We are tracking this work internally. label Jan 23, 2024
@MicrosoftEdge MicrosoftEdge deleted a comment from github-actions bot Jan 23, 2024
@MicrosoftEdge MicrosoftEdge deleted a comment from github-actions bot Jan 23, 2024
@monica-ch
Copy link
Contributor

@lezzi Could you try navigating to microsoft.com, open a print dialog (ctrl+p) and check if its reproes with the site.

The dmp suggest that it was SmartScreen feature. Could you try to disable SmartScreen feature and see if it makes a difference? To disable SmartScreen, you could set IsReputationCheckingRequired to false after webview is created.

@lezzi
Copy link
Author

lezzi commented Jan 23, 2024

@monica-ch

@monica-ch
Copy link
Contributor

@lezzi Have you navigated after the smart screen is disabled? If it still reproes, please share the latest dmp.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working tracked We are tracking this work internally.
Projects
None yet
Development

No branches or pull requests

3 participants