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] MSVCP140.dll silent crash #1240

Closed
BoringName15 opened this issue Nov 23, 2024 · 6 comments
Closed

[Bug] MSVCP140.dll silent crash #1240

BoringName15 opened this issue Nov 23, 2024 · 6 comments
Labels
state:Done This issue has been resolved/dismissed type:Bug Something isn't working

Comments

@BoringName15
Copy link

BoringName15 commented Nov 23, 2024

I've already solved this issue by updating microsoft C++ redistributables but I think how the error was handled is a problem and worth letting you know.

Video2x would immediately close on my second machine with no errors even with logging enabled. Using the command line was the same. It would just close immediately with no errors listed.

I had to check windows event viewer to see details of the crash and that it was caused by an exception from MSVCP140.dll

The system was on version 14.28, once I updated the redistributables, the new version of 14.42 worked successfully.

If it's possible maybe set a minimum runtime version required and prompt the user to update if the system is below this version.

Also, you probably already know but some of the command line documentation on the wiki page is out of date. Specifically related to ffmpeg extra encoder options.

edit: just to clarify it would crash when I clicked start.

@github-actions github-actions bot added the state:Backlog This issue will be worked on in the future label Nov 23, 2024
@k4yt3x k4yt3x added type:Bug Something isn't working state:Planned This issue is already scheduled to be worked on and removed state:Backlog This issue will be worked on in the future labels Nov 25, 2024
@k4yt3x
Copy link
Owner

k4yt3x commented Nov 25, 2024

Thanks for reporting the issue. I originally checked for the VC runtime version in the installer, but its registry keys don't seem to work correctly (e.g., the installed key is set to true even after VC runtime is removed). Then I moved to check if the VC library files exist.

I'll add the version checks back.

@BoringName15
Copy link
Author

Keep in mind some people don't use the installer. I just extracted the zipped version to a folder and ran it from there.

@k4yt3x
Copy link
Owner

k4yt3x commented Nov 25, 2024

That's a good point. I don't have any good ideas for that to do for that case though since my binary wouldn't even run. I can't add code that will give a meaningful prompt or anything.

@BoringName15
Copy link
Author

It did run in the case I reported, it didn't crash until I clicked "Start" so I'd assume in theory you could do a check when Start is clicked and abort the process if the version is too old to avoid the crash then notify the user to update the runtime libraries.

@k4yt3x
Copy link
Owner

k4yt3x commented Nov 25, 2024

Ah I see that's different. I'll need to do some experiments to see how to best handle it.

@k4yt3x
Copy link
Owner

k4yt3x commented Dec 21, 2024

Added a check in the new version to prompt the user if the VC runtime version is below 14.42.

@k4yt3x k4yt3x closed this as completed Dec 21, 2024
@github-actions github-actions bot added state:Done This issue has been resolved/dismissed and removed state:Planned This issue is already scheduled to be worked on labels Dec 21, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
state:Done This issue has been resolved/dismissed type:Bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants