-
Notifications
You must be signed in to change notification settings - Fork 20
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
pypardiso
(PyPI): Error libiomp5md.dll
already initialized
#58
Comments
pypardiso
: Fatal Python Error (libiomp5md.dll
already initialized)
pypardiso
: Fatal Python Error (libiomp5md.dll
already initialized)pypardiso
installed via PyPI: libiomp5md.dll
already initialized
pypardiso
installed via PyPI: libiomp5md.dll
already initializedpypardiso
(PyPI): Error libiomp5md.dll
already initialized
Hi @adtzlr, I have a noticed the same today, but haven't found time to look into it yet. I have a pipeline that runs every 24h and runs the tests and since this morning all windows pypi tests fail: https://github.com/haasad/PyPardisoProject/actions I assume there's been a new release of one of the dependencies, which breaks pypi pypardiso. I'll get back to you once I know more. |
Hi, perfect! I found some questions on stackoverflow related to that, like https://stackoverflow.com/questions/20554074/sklearn-omp-error-15-initializing-libiomp5md-dll-but-found-mk2iomp5md-dll-a The WinPython distribution comes pre-bundled with a version of |
There was indeed a new release of mkl 2024.0.0 and intel-openmp 2024.0.0 on 14th of November (for windows and linux). Downgrading MKL should get rid of the error:
I'm still deciding how to proceed, I could in theory make a new pypardiso release which pins mkl to <2024. But I'm probably going to wait a few days and hope that this is fixed upstream. |
It's strange, IIRC a similar thing happened last year when Intel released mkl2023... |
Hello @haasad, I am the product manager for MKL at Intel and I've been looking for issues in GitHub since our latest release (2024.0.0) to be sure we can keep improving the quality of our releases. Do you know if the issue described here happens with WinPython only? Were you able to reproduce the issue in other configurations or Operating Systems? |
@haasad there are 2 workarounds to make the tests pass using mkl==2024.0.0 on Windows/Conda environment described in the link below: |
@haasad I am happy to inform that we have 2 good versions of intel-open for Windows that solve this issue in the correct way:
I already tested pypardiso master branch for both versions, that means you can close this issue and revert the pin to mkl<2024. Let me know if you have any question. |
Hi @ghsilva, thanks for the heads-up. I couldn't completely remove the pin, because the new releases aren't yet available on conda-forge. But it looks like the folks at https://github.com/conda-forge/intel_repack-feedstock are working on it. I opted for excluding I'm closing this issue. Thanks for your efforts 👍 |
for future reference: #71 (comment)
|
Hi @haasad!
For Win10, WinPython 3.11.5 and PyPardiso installed via PyPI I get a
Fatal Python error: Aborted
if I try to use PyPardiso with FElupe. However, I'm nearly 100% sure that this is not related to FElupe as it works with the sparse-solver from scipy.A minimal code that crashes using FElupe (it works with the sparse-solver from scipy) (
pip install felupe
):I finally tracked this down to a lib-error. Do you have any advises for that?
This one works, but as described above this is not a very good idea.
The text was updated successfully, but these errors were encountered: