Replies: 1 comment
-
UPD: The CRYPTO_atomic_read() function is not in libssl-1_1-x64.dll, but in libcrypto-1_1-x64.dll, which is bundled with WeBots. The error box indeed said "libssl-1_1-x64.dll", no mistake here. The error disappeared after the user removed 'Intel(R) Management Engine' from his computer. Still very strange. So this situation probably doesn't require any action, except that maybe a notice somewhere that WeBots can conflict with 'Intel(R) Management Engine'. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Hi,
On Windows, a user reported error "CRYPTO_atomic_read() not found in libssl-1_1-x64.dll". The version it can't load is from the 'Intel(R) Management Engine'. I understand that various versions of libssl are shipped with many softwares, so having a version mismatch on this DLL would not be a surprise.
However, it appears that 2022b does not even use libssl, even while running controllers and robot windows, or at least I couldn't see it using LoadedDllView from https://www.nirsoft.net/utils/loaded_dll_view.html.
Beta Was this translation helpful? Give feedback.
All reactions