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

OpenFileDialog / SaveFileDialog will shutdown WPF application with Error #10318

Open
samanoudi opened this issue Jan 19, 2025 · 6 comments
Open
Labels
Investigate Requires further investigation by the WPF team.

Comments

@samanoudi
Copy link

samanoudi commented Jan 19, 2025

Description

have an issue using OpenFileDialog/ SaveFileDialog in .NET 9.0 WPF Application. When shown the Dialog and hovering/clicking with the mouse on the Drive selection parts the WPF app will exit with the following error :

The program '[32780] WPFTESTS.exe' has exited with code 3221226505 (0xc0000409).

Image

Note: Using the Quicklinks, and Selecting Files is working without any Errors. Reverting the Application to Target .NET 8 the error will go away. This is calling method.

Reproduction Steps

private void Button_Click(object sender, RoutedEventArgs e)
{
OpenFileDialog f= new OpenFileDialog();
f.ShowDialog();
}

Expected behavior

Opening a FielDialog and selecting drives, folder and files

Actual behavior

App Shuts down with Error

Regression?

.Net8

Known Workarounds

No response

Configuration

Windows 11
Net9 var 9.102

Other information

No response

@filipnavara
Copy link
Member

This could be caused by a 3rd-party shell extension, possibly in tandem with the CET stack protection that is enabled by default for all .NET 9 apps. Can you enable the Windows Error Reporting to produce a memory dump for the crash (https://learn.microsoft.com/en-us/windows/win32/wer/collecting-user-mode-dumps)? That can be analyzed to find the culprit.

@lindexi
Copy link
Member

lindexi commented Jan 20, 2025

@samanoudi Sorry, I can not repro your issues in my WPF demo. And I agree with @filipnavara .

By the ways, you can fire the wpf issues to https://github.com/dotnet/wpf/issues

@h3xds1nz
Copy link
Contributor

h3xds1nz commented Jan 20, 2025

This would a duplicate of #10305 then.

I wonder, is dotnet/runtime#109548 out yet? Milestone is set to 9.0.2. Given the shadow stack fail with FAST_FAIL_SET_CONTEXT_DENIED.

@filipnavara
Copy link
Member

filipnavara commented Jan 20, 2025

This would a duplicate of dotnet/wpf#10305 then.

Yep, looks like the same issue.

I wonder, is #109548 out yet? Milestone is set to 9.0.2. Given the shadow stack fail with FAST_FAIL_SET_CONTEXT_DENIED.

No, it's not out yet. 9.0.2 will be released on February 11, 2025. (SDK 9.0.103 or 9.0.200)

You can check the commit history of https://github.com/dotnet/runtime/commits/v9.0.1/ and see that it didn't make it to 9.0.1.

@h3xds1nz
Copy link
Contributor

No, it's not out yet. 9.0.2 will be released on February 11, 2025. (SDK 9.0.103 or 9.0.200)

You can check the commit history of https://github.com/dotnet/runtime/commits/v9.0.1/ and see that it didn't make it to 9.0.1.

Felt easier to ask, not gonna lie.

@jeffschwMSFT jeffschwMSFT transferred this issue from dotnet/runtime Jan 21, 2025
@lindexi
Copy link
Member

lindexi commented Jan 22, 2025

@samanoudi Could you try #10305 (comment) ?

<CETCompat>false</CETCompat>

@lindexi lindexi added Investigate Requires further investigation by the WPF team. and removed Untriaged labels Jan 22, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Investigate Requires further investigation by the WPF team.
Projects
None yet
Development

No branches or pull requests

4 participants