-
Notifications
You must be signed in to change notification settings - Fork 230
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
Dependency issue causes significant memory leak on RMG Py3 #1850
Comments
@mliu49 @amarkpayne @mjohnson541 |
I think this is most likely due to rdkit/rdkit#2639. We do a lot of RDKit atom creation during RMG jobs (for aromaticity perception and identifier generation). The timing for their fix to the issue also seems to align well. If we confirm this, then we should increase the RDKit version requirement in our environment file. |
Indeed, taking the good rmg_env and downgrading to rdkit 2019.03.4.0 reproduces the memory leak exactly. Interestingly, the mystery 5th process when requesting 4 processors is not present; so this is either due to another dependency or perhaps how that dependency interacts with the RMG server vs Erebor. Either way, the conclusion is to update the rdkit version using |
Closing since this change was implemented. I will, however, tag this issue in the latest RDKit upgrade that we are undergoing. |
Bug Description
Significant memory leaks have been observed when using an rmg_env created around early Oct 2019. Memory leaks are not observed when using a recently created rmg_env, whose various dependencies are at an updated version.
Below is the output from diffing the output from conda list from the two rmg_env (this output is tab spaced and easier to read that exporting the environment and diffing the yml files). The older rmg_env is listed first, hence the older version number for each dependency.
It is unclear which of these dependencies is responsible for the memory leak, but no memory leak is observed with the newer dependencies. The recommendation is to remove and recreate the rmg_env if you created an rmg_env for Python 3.7 around early Oct 2019 and you think you are experiencing memory leaks. Using the exact dependencies in this file resolves the issue (just change the extension to .yml since GitHub only lets me upload .txt files, not .yml files), though just using
conda env create -f environment.yml
and letting conda pull the latest dependencies should also work well.Functional_rmg_env.txt
How To Reproduce
Recreating an rmg_env with the identical dependencies using this yml file should reproduce the issue, but don't do that to yourself! (GitHub doesn't let me upload .yml files. Just change the extension from .txt to .yml)
Memory_Leak_mg_env.txt
The text was updated successfully, but these errors were encountered: