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

App Crash: Faulting module name: ucrtbase.dll #162

Open
NickSebClark opened this issue Nov 13, 2023 · 4 comments
Open

App Crash: Faulting module name: ucrtbase.dll #162

NickSebClark opened this issue Nov 13, 2023 · 4 comments

Comments

@NickSebClark
Copy link

NickSebClark commented Nov 13, 2023

Hi

I've installed 23.1.9 using the system wide deploy tool on Windows Server 2022.

When I try to run my app it immediately crashes.

Event viewer shows:

Faulting module name: ucrtbase.dll, version: 10.0.20348.1, time stamp: 0xdacb234c
Exception code: 0xc0000409

Any ideas?

Other attempts:

MinGW version 23.2.1 per-app-deployment
This results in zlib1.dll not found.
I've tried llvmpipe and softpipe

@pal1000
Copy link
Owner

pal1000 commented Nov 14, 2023

Hi

I've installed 23.1.9 using the system wide deploy tool on Windows Server 2022.

When I try to run my app it immediately crashes.

Event viewer shows:

Faulting module name: ucrtbase.dll, version: 10.0.20348.1, time stamp: 0xdacb234c Exception code: 0xc0000409

Any ideas?

Please try 23.2.1 and 23.3.0-rc3 MSVC builds. 23.1 branch is EOL so it will never be fixed. If you still have problems you need to collect a call stack. Debug symbols are in MSVC debug info package.

Other attempts:

MinGW version 23.2.1 per-app-deployment This results in zlib1.dll not found. I've tried llvmpipe and softpipe

This is odd. I need to run some tests to see if I can reproduce this error.

@pal1000 pal1000 self-assigned this Nov 14, 2023
@pal1000
Copy link
Owner

pal1000 commented Nov 14, 2023

Other attempts:
MinGW version 23.2.1 per-app-deployment This results in zlib1.dll not found. I've tried llvmpipe and softpipe

This is odd. I need to run some tests to see if I can reproduce this error.

I was able to reproduce and after testing most MinGW builds between 23.1.2 and 23..2.1 I think this is a different way of how #156 manifests.

@pal1000 pal1000 removed their assignment Nov 14, 2023
@NickSebClark
Copy link
Author

So to confirm we think the MinGW build is just broken and we have to wait for it to be fixed?

@pal1000
Copy link
Owner

pal1000 commented Nov 15, 2023

Yes and I think it will stay broken until this passes review and gets merged.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants