-
Notifications
You must be signed in to change notification settings - Fork 562
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
CRASH "library initializer failed" on Windows SDK 10.0.26100.0 #6962
Comments
Thank you for the detailed report. Adding back the newlines to the log from above:
It looks like it's the myclient itself, and not some system library, that crashed: Would it be possible for you to run under a debugger and get the callstack of the Access Violation at 0x00000000150ffec7? |
You're welcome! I found out that the second to last insturction before crashing is the Below is my full WinDBG output:
(Edit: with dynamorio PDBs loaded) |
Extends the private loader bcrypt.dll entry failure being ignore to ignore all private library entry failures. We have had multiple cases of initializers failing without fatal consequences, and given that we do not have resources to track down every detail it is best to note the failure and move on. We have seen Dr. Memory in particular fail on newer Windows versions and in some cases ignoring that failure lets the tool continue and succeed, as only a small piece of the private library is needed (generally pulled in as a chain of dependences from dbghelp.dll which is used for symbol information). The private loader on Windows is considered best-effort at this point. Issue: #6570, #6962
Though it would be best to fully understand and address the issue, lack or resources may prevent that in the short term. #7003 may work around it, as many times only a small fraction of a private library is really needed (these chains of dependent libraries end up pulled in just for small features used by clients) and side failures can be ignored and tolerated. Does everything else work fine if #7003 is applied and the init issue becomes non-fatal? |
Describe the bug
On Windows, when compiled with Windows SDK 10.0.26100.0, clients would crash with "library initializer failed". This occurred on multiple clients, including the "empty" sample client. This does not occur when compiled with older SDKs.
To Reproduce
Steps to reproduce the behavior:
CMakePresets.json
:drrun.exe
Please also answer these questions:
Screenshots or Pasted Text
Command prompt output of injecting a simple client into
tasklist
:Excerpts from log 0:
Excerpts from the app log:
Versions
The text was updated successfully, but these errors were encountered: