-
-
Notifications
You must be signed in to change notification settings - Fork 25.9k
Persistent UserWarning about KMeans Memory Leak on Windows Despite Applying Suggested Fixes #30921
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
Comments
Thanks for the report.
Have you checked the output of Please include the full output of
Using OpenBLAS should fix the problem. See the precise conditions that lead to this warning to be raised in the source code: scikit-learn/sklearn/cluster/_kmeans.py Lines 910 to 928 in d0ee195
BTW, next time, please use markdown formatting to make the issue more readable (I edited it myself this time). |
Closing as lack of response from the OP. |
Uh oh!
There was an error while loading. Please reload this page.
Describe the bug
Issue Description
When running code involving GaussianMixture (or KMeans), a UserWarning about a known memory leak on Windows with MKL is raised, even after implementing the suggested workaround (OMP_NUM_THREADS=1 or 2). The warning persists across multiple environments and configurations, indicating the issue may require further investigation.
Warning Message:
Steps to Reproduce
1-Code Example:
Environment:
OS: Windows 11
Python: 3.10.12
scikit-learn: 1.3.2
numpy: 1.26.0 (linked to MKL via Anaconda)
Installation Method: Anaconda (conda install scikit-learn).
Expected vs. Actual Behavior
Expected: Setting OMP_NUM_THREADS should suppress the warning and resolve the memory leak.
Actual: The warning persists despite environment variable configurations, reinstalls, and thread-limiting methods.
Attempted Fixes
Set OMP_NUM_THREADS=1 or 2 in code and system environment variables.
Limited threads via threadpoolctl:
code:
Reinstalled numpy and scipy with OpenBLAS instead of MKL.
Tested in fresh conda environments.
Updated all packages to latest versions.
None of these resolved the warning.
Additional Context:
The warning appears even when using GaussianMixture, which indirectly relies on KMeans-related code.
The issue is specific to Windows + MKL. No warnings on Linux/Mac.
Full error log: [Attach log if available].
Questions for Maintainers:
Is there a deeper configuration or bug causing this warning to persist?
Are there alternative workarounds for Windows users?
Is this issue being tracked in ongoing development?
Thank you for your time and support!
Let me know if further details are needed.
Steps/Code to Reproduce
Expected Results
Actual Results
Versions
The text was updated successfully, but these errors were encountered: