-
Notifications
You must be signed in to change notification settings - Fork 3k
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
Release version of onnxruntime.dll has a dependency on dbghelp.dll #21826
Comments
Thanks for flagging & spotting this -- is the unnecessary dependency causing any performance issues for you or larger package sizes? |
One of our customers complains that they are not able to load our DLL while using |
We are waiting on more task but this should be resolved early next week |
I can confirm 1.18.1 release does not have the issue but the latest one(1.19.0) has it. |
The commit id 8749fa3 seems to be fine. |
It is because PR #21410. |
The dep is pulled by abseil's symbolize library. |
Unfortunately, there is no formal way to disable it: abseil/abseil-cpp#1363 |
### Description This change disables Abseil's symbolize functionality in Windows non-debug builds. ### Motivation and Context To solve #21826. Avoid having a dependency on dbghelp.dll.
### Description This change disables Abseil's symbolize functionality in Windows non-debug builds. ### Motivation and Context To solve #21826. Avoid having a dependency on dbghelp.dll.
Describe the issue
Release version of onnxruntime.dll has a dependency on dbghelp.dll (using functions SymInitialize, SymFromAddr, SymSetOptions) while this functionality is not needed in a release build.
This is a regression, likely caused by #21300 (2024-07-10).
To reproduce
.\build.bat --config RelWithDebInfo --build_shared_lib
dumpbin /imports onnxruntime.dll
Urgency
No response
Platform
Windows
OS Version
Any
ONNX Runtime Installation
Built from Source
ONNX Runtime Version or Commit ID
1.19
ONNX Runtime API
C++
Architecture
X64
Execution Provider
Default CPU
Execution Provider Library Version
No response
The text was updated successfully, but these errors were encountered: