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

OpenMP Runtime Initialization Conflict (libiomp5md.dll) in scripts/ocr.py #202

Open
Spagestic opened this issue Jan 18, 2025 · 0 comments
Open

Comments

@Spagestic
Copy link

Description

Multiple instances of OpenMP runtime (libiomp5md.dll) are being initialized simultaneously, causing potential performance degradation and reliability issues.

Command Executed

!python scripts/ocr.py --config configs/ocr.yaml

Error Message

OMP: Error #15: Initializing libiomp5md.dll, but found libiomp5md.dll already initialized.
OMP: Hint This means that multiple copies of the OpenMP runtime have been linked into the program. That is dangerous, since it can degrade performance or cause incorrect results. The best thing to do is to ensure that only a single OpenMP runtime is linked into the process, e.g. by avoiding static linking of the OpenMP runtime in any library. As an unsafe, unsupported, undocumented workaround you can set the environment variable KMP_DUPLICATE_LIB_OK=TRUE to allow the program to continue to execute, but that may cause crashes or silently produce incorrect results. For more information, please see http://www.intel.com/software/products/support/.

Temporary Solution

# Set OpenMP environment variable to avoid runtime conflicts in scripts/ocr.py
os.environ['KMP_DUPLICATE_LIB_OK'] = 'TRUE'
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant